gardener, Interface administrators, Administrators
1,540
edits
Changes
Jump to navigation
Jump to search
There's a Python script <tt>contextproject.py</tt> at Hraban's [http://github.com/fiee/tools/blob/master/contextproject.py github repository] to help creating the files (.ini files can be used for initial content). This functionality would be nice to be integrated in any editor supporting ConTeXt... '''Summary (for MkIV)'''==Comand behaviour==
added subtitles
< [[The ConTeXt Way]] | [[Structurals]] >
==Introduction==
ConTeXt knows no document classes (as LaTeX does). You can define your [[Layout|layout]] yourself. If you use the same layout for several products, save it as an '''environment''' file.
In addition, you have to keep in mind that when compiling a product or component file, ConTeXt goes "up" to the project file and compiles everything it finds in there that is not a <cmd>product</cmd> (e.g. table of content, sectioning commands, text, <cmd>component</cmd> etc.). So all the things on project level have to be put inside a <cmd>product</cmd>, otherwise they will show up in the individual components (or products), too. That also makes it problematic to use <cmd>component</cmd> directly inside a project file, i.e. you have to use <cmd>product</cmd>, you can't skip it.
==Naming conventions==
[[User:Hraban|Hraban]] uses and suggests the following naming conventions
* c_foo
* env_foo
There's a Python script <tt>contextproject.py</tt> at Hraban's [http://github.com/fiee/tools/blob/master/contextproject.py github repository] to help creating the files (.ini files can be used for initial content). This functionality would be nice to be integrated in any editor supporting ConTeXt...
==Example files==
'''Project'''
</texcode>
Depending on the (start-stop) environment a command will either load a file once, or many times or not at all. The following table specifies what happens when:
