Difference between revisions of "Talk:Inside ConTeXt"

From Wiki
Jump to navigation Jump to search
(Added suggestion: document location of macro definitions in the source.)
Line 12: Line 12:
 
** I propose starting with a really barebones XML file that only lists the macros themselves (no invocation syntax), then add the correct definitions interactively using texshow-web itself.
 
** I propose starting with a really barebones XML file that only lists the macros themselves (no invocation syntax), then add the correct definitions interactively using texshow-web itself.
 
--[[User:Taco|Taco]]
 
--[[User:Taco|Taco]]
 +
 +
One thing that might be useful to include with this (and possibly with rest of texshow) is where the commands are defined.  Since a lot of commands are definied somewhat implicitly (rather than with code that names them directly -- consider, for instance, what happens if one runs \definestartstop{} or the like), it's often hard to find such things in the code just by grepping for them.
 +
 +
Then again, what would probably be really useful for this is some way to do it that allows us to provide the results back to Hans in a form that he can turn into comments for the code.
 +
 +
--[[User:Brooks|Brooks]]

Revision as of 00:21, 6 August 2004

It would make sense to have texshow-style documentation for the low-level macros. How about Commands::getparameters et. al. ? Or \getparameters ?

  • yes, it would make much sense, but not in here. We should add them to texshow*, so they would be available not only to the online users but also to etexshow and perhaps other xml based texshow out there.
    • who does the job? The commands have to be given in an xml format, wich is not that trivial (but not complex either)
    • how do we keep the user interface of texshow(-whatever) clean? I would have to program some kind of filter based on keywords - but I wanted to do this anyway :-)
    • I'll post some more on this topic soon, since I'll work on texshow for a bit now

--Patrick Gundlach 11:12, 5 Aug 2004 (CEST)

  • The initial comment was me (I keep getting logged out for discernable reason).
    • It seems to me that the best way to do this is to consider the programmer-level macro's to be an extra interface (named 'api').
    • I volunteer for the creation of (at least the beginnings of) the needed XML.
    • I propose starting with a really barebones XML file that only lists the macros themselves (no invocation syntax), then add the correct definitions interactively using texshow-web itself.

--Taco

One thing that might be useful to include with this (and possibly with rest of texshow) is where the commands are defined. Since a lot of commands are definied somewhat implicitly (rather than with code that names them directly -- consider, for instance, what happens if one runs \definestartstop{} or the like), it's often hard to find such things in the code just by grepping for them.

Then again, what would probably be really useful for this is some way to do it that allows us to provide the results back to Hans in a form that he can turn into comments for the code.

--Brooks