984
edits
Changes
m
no edit summary
* The initial comment was me (I keep getting logged out for discernable reason).
*** I clean up <tt>/tmp</tt> after one week, so non-cookie-sessions will be deleted then. Is this too short? --[[User:Patrick Gundlach|pg]]
** 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').
*** OK, I'll add something. --[[User:Patrick Gundlach|pg]]
**** done --[[User:Patrick Gundlach|pg]] 01:02, 12 Aug 2004 (CEST)
** I volunteer for the creation of (at least the beginnings of) the needed XML.
*** great, if you have a few to start with, just mail them to me, OK? [[User:Patrick Gundlach|pg]]
** 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]]
Side note: I once started documenting some of ConTeXt 'for programmers', see [[http://tex.aanhet.net/context/syst-gen-doc.pdf syst-gen documentation]].
--[[User:Taco|Taco]]
I agree that we need a formal description of the low-level user commands in ConTeXt. I'll provide an new interface for texshow-web. But this will be xml-only, so there would no way to use the descriptions in the regular texshow until the regular texshow reads xml. I think that we need a file pointer, but not necessarily an exact line. It would help though if all commands that we describe in the "texshow-api" would be described with the <tt>\macros{...}</tt> macro.
--[[User:Patrick Gundlach|pg]] 21:33, 11 Aug 2004 (CEST)