On Thu, 7 Mar 2002 10:01, Bill Burton wrote: > Yes. I was occupied tracking down a bug in jaxen which is used by dom4j > which is used by DVSL. With that fixed, I'm now able to generate > correctly formatted pages for the datatypes as well as tasks with only > minor changes to the existing stylesheet. Now that this is working, I'll > look at generating a tasks and datatypes overview page.
excellent! > Something I'm considering in the short run, is to ignore the categories > and generate the XML (and respective HTML) in the same directory structure > currently used. For the most part, the new doc would be a drop in > replacement for the old. Links to ../CoreTypes, etc. everywhere would > still work. The category meta info would still be used to generate an > overview page but it would have nothing to do with the physical location > of the files. +1 > What I'd really like is a way of specfying how tasks are classified into > categories at the Ant task level much the way the <group> element works > for javadoc or in an XML file. That allows much more flexibility in how > things are organized over hard coding all categories in the @ant.task tag > in each task source file. Which categories a task belongs to is strictly > a documentation issue and not at all related to the behavior of the task. +1 -- Cheers, Pete --------------------------------------------------------------- The difference between genius, and stupidity? Genius has limits --------------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
