> -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 05, 2004 4:30 PM > To: Maven Developers List > Subject: RE: xdoc with custom templates and/or navigation > > > On Wed, 2004-05-05 at 08:53, [EMAIL PROTECTED] wrote: > > Is there a recommended way to modify the navigation menu? > > I don't know what you're trying to do. If you're changing the > structure > of the xhtml then you can take a look at: > > http://www.pols.co.uk/downloads/static-mesh/ > > The primary goals of the new xdoc plugin are speed and > efficient use of > memory where themes are control entirely via css, not changing the > structure of the output. >
That's fine! > So using something like Jelly/JSL I'm not even vaguely considering > because we can't even generate the plugin site without it > crapping out. > If there is something that is comensurable with the goals of speed and > efficiency then I would incorporate it. There are some things that Joe > Walnes is working on in XStream for doing XML transformations in an > extremely efficient manner so that I would possibly incorporate. > Jason why you are assuming that the only solution which will allow higher degree of customisation is to make xdoc plugin configurable/customisable and template based? It's the site plugin which should be customisable and there you could be able to choose how do you want to transform your xdocs. AFAIK: SiteMesh and such tools are easy you use if you want to add some things to pages. But they are not so easy to use when you want to remove parts of the pages. IMO it will be much simpler and way faster to do xdoc2html or xdoc2flash thing then doing xdoc2xhtml with your super fast xdoc plugin and then xhtml2html or xhtml2flash with sitemesh When maven will be based on plexus it will just mean that somebody should be able to drop his component which will be used by site plugin to perform xdoc transformation. It's not something more complex then that. Optimised components are cool and we should promote this way of thinking. But they are also very small classes which are super easy to rewrite and first of all they are _components_!!. It means they are _replaceable_. Why one should use things like sitemesh when he can quickly write his own component which will be also optimised for speed, memory usage and efficiency and in addition will match requirements of this person or his organization. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]