Mojca Miklavec wrote:
Here's some more work for you Patrick, in case you get bored.
(I guess I'll soon be removed from the list as a spammer/abuser if I
continue writing mails such as this one :)
What do the others think about it?
some day others will start expecting you to help patrick gardening -)
Take \setuplayout for example. Describing such huge collection of
parameters in plain text is not clear, synoptic any more. It would be
great if there would be a possibility to add descriptions for:
- the command as such (already there)
- every pair of braces (only one for \setuplayout), has to be visible
if it is optional or not
- every parameter inside a single brace
- every single option for that parameter (for example: width=middle
means that ...), default has to be marked
default maring is a bit tricky (since it can be \SomeCommand which will they
blow up context visualizer; in principle, now that we've moved to xml for the
descriptor, it's easier to add features.
can you give a more verbose example
The ability to add commands is already there I think (I have never
tried it out yet). What about adding commands for (official and
third-party) modules? It should be separated from the main page, but
still offering the same functionality.
in principle each module should have an associated spec file
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
