On Sat, 27 Jul 2002 01:58, Nicola Ken Barozzi wrote: > So, Peter, how does this look. > Is it ok for you? > > Is there something missing?
No idea - havent checked yet - though I notice that the website is still looking fairly crap so I can't say I am inspired. I'll reiterate what I want again. * Simple task to call so I can have different pipelines (changes vs normal document vs faqs) work. * I want to be able to include/exclude files based on ant includes/ecludes * I want only the files that have been changed to be updated * I want zero copying about * I want 15 second build time max * I want to be able to have all the links in menu to be relative to base of site, not base of page they are in. SO I can put docs in bdg/foo.xml and has all links work gracefully * I want no dates or build specific data to be stored in generated docs (because causes pain when updating online docs). * I want nice output. Similar to ... [cocoon] Generating doc: foo.html [cocoon] Generating doc: bdg/foo.html [cocoon] Error Generating doc: bar.html (<a> on line 15 must be terminated with a </>) One thing that I have not said before but I would like to have is the following. I would like to be able to add in a construct like <code-link class="org.apache.avalon.framework.Version">the Version</code-link> or <code-link class="org.apache.avalon.framework.Version"/> (which defaults to using short classname as text for link). This would then link to the appropriate uri for class javadoc. I would like it to work in a way similar to javadoc links. So you can have multiple api base dirs (ie phoenix docs could link to framework code). -- Cheers, Peter Donald ------------------------------------------------------------- | Egoism is the drug that soothes the pain of stupidity. | ------------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
