Monday, January 21, 2002 Taco Hoekwater wrote:
>> >I use pre-existent core and add-on modules to get the ideas for >> >mine. Much of my knowledge of ConTeXt internal comes from studying >> >the sources (of course, if Hans used English instead of Dutch, it >> >would ease my work a lot ;-> but he's working along this path). TH> Same for me. Just reading the source is a good idea, and using TH> something like 'grep' or 'ctags' helps a lot. Yeah, and being Dutch helps even more ;-) >> also, the modules should have t-* names, no m-* or else TH> or else what? ;) TH> This functionality is already in ConTeXt, Hans? It is indeed because the modules I use have the t- prefix. TH> Same for me. I already have too much to read as it is. However, TH> I could set up a public forum for ConTeXt support if there are TH> people interested. There is not much request for ConTeXt help on comp.text.tex; rather than creating a new forum, you could simply follow the newsgroup and filter out all non-pertinent posts (that is, most of them ;->) >> >Another thing developers would need is a module interface to >> >TeXUtil: when a ConTeXt module requires some particular >> >postprocessing, it should provide a Perl module to be loaded by >> >TeXUtil. >> >> it maybe that texexec will control all of this TH> Not sure about that, extensions usually don't need texexec TH> but texutil. Usually, you want to put some extra info in the tui TH> file. It makes more sense to do this from texutil directly. This is precisely my view of it. Hans, you could get an idea of what is needed by giving a look to my xdesc module (and the relative, patched, texutil) -- Giuseppe "Oblomov" Bilotta
