Hello Syndicate, Jérôme Laurens, maker of iTeXMac, is being *very* ambitious for his 2.0 version, and he contacted me for some ideas/contributions on the ConTeXt side of things. First, he wanted some sample documents and/or templates. Since every iTeXMac document is actually a directory, and it is project-based, I was wondering if there were any folks who had good examples using products/ environments. Yes, I'm keeping my eye on the released manuals. :) Secondly, he asked which texexec were the best to expose in the GUI. I came up with this list off the top of my head: --mode= --usemodule= --xmlfilter= --environment= --batch --once --runs= (The engine switches will probably be set on a project level, he said, and --pdfarrange and the like would probably be exposed in another GUI helper.) Is there anything else really compelling to expose in a GUI? Hans, he also has the ability to point at different source trees on a preference and project basis. I will look at the minimal trees, to see what needs to be done to support them within his framework. Mac users can take a look at the rough but promising project here: <http://sourceforge.net/project/showfiles.php? group_id=58056&package_id=53754> (currently iTeXMac2 preview8) -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Adam Lindsay wrote:
Hello Syndicate,
J�r�me Laurens, maker of iTeXMac, is being *very* ambitious for his 2.0 version, and he contacted me for some ideas/contributions on the ConTeXt side of things.
First, he wanted some sample documents and/or templates. Since every iTeXMac document is actually a directory, and it is project-based, I was wondering if there were any folks who had good examples using products/ environments. Yes, I'm keeping my eye on the released manuals. :)
Secondly, he asked which texexec were the best to expose in the GUI. I came up with this list off the top of my head: --mode= --usemodule= --xmlfilter= --environment= --batch --once --runs=
(The engine switches will probably be set on a project level, he said, and --pdfarrange and the like would probably be exposed in another GUI helper.)
- go for 'texmfstart texexec' - for options etc, maybe using the ctx jobfile is a option (see recent manual) for modules and env's - xml filters are normally loaded in styles - --mode and --batch make sense to support at the gui level - how about predefined options, like: texmfstart texexec --list <filename> and alike?
Is there anything else really compelling to expose in a GUI?
the previewer
Hans, he also has the ability to point at different source trees on a preference and project basis. I will look at the minimal trees, to see what needs to be done to support them within his framework.
- a setuptex.tmf file (see distribution) - texmfstart --tree=/blabla/mytex texexec ... Hans
participants (2)
-
Adam Lindsay -
Hans Hagen