At 10:26 AM 7/27/2002 +0200, you wrote:
>It's always looked 'fairly crap'.
Look at the extension page. It looked good a month ago and now it does not.
> I'll reiterate what I want again.
> >
> > * Simple task to call so I can have different pipelines (changes vs normal
> > document vs faqs) work.
>
>could you elaborate? You want to generate changes using a different task
>or a different task configuration? Seems to me like it is way easier to
>just have a single task that does all your docs.
I want one task capable of handling different types/dtd/schemas foir docs.
One can be a todo list, another change list, another faqs and the remainder
docs. And I dont want to have to alter some master sitemap doc that is in
some other cvs or whatever.
so you mean the base for the reference of links in /phoenix/bdg/menu.xml
>should be /phoenix and not /phoenix/bdg?
>
>I'm not too happy with that, I think. I like the idea that each
>subdirectory is a separate 'documentation subproject'.
Thats not an opinion I share. Everything that the user saids is in one menu
should be in one menu, directorys are useful tools to categorize or else
you end up with documents with names 20 characters long.
Cheers,
Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Faced with the choice between changing one's mind,
and proving that there is no need to do so - almost
everyone gets busy on the proof."
- John Kenneth Galbraith
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
