> Yes, it was the entire change of the plugin I wasn't kosher with as it changed entirely the css and markup and broke the theme work Bob did. I definitely want to maintain what Bob originally had because it is the first plugin I intend to swap out partially for the pure java version, the first phase being simply the xdoc -> xhtml transformation which is entirely doable as a first step. This is why I was highly hesitant on processing the massive set of changes. So you are saing that you're going to revert any change to the xdoc plugin while migrating to maven2? And that you want to "freeze" the xdoc plugin development waiting for m2? That's the point in my previous mails... I'm not against maven2 at all, I like the idea to avoid use of jelly everywhere, but this hard line between jelly/POJOs plugins is going to cause problems... Why not start fixing the actual xdoc plugin step by step replacing jelly with some java code and trying to not to revert existing functionalities instead of trashing it?
BTW, I understand you can not agree with my changes to the xdoc plugin, but I think there were lots of reasons for those: - the xhtml generated by the old xdoc plugin was wrong. The new one produces valid xhtml - the size of the generated xhtml was ugly due to whitespace. The new one produces files 1/3 size whithout destroying html. - the new plugin allows users to totally customize the layout using only css. You should not ever need to supply a custom site.jsl (IHMO this should not be allowed -since not needed-, I agree with you for this direction on m2). Being the new layout totally tableless you can choose the position of elements in the page and manipute them using css (thanks to added classes and IDs). - probably you haven't ever looked at generated website using IE instead of mozilla... sites generated by the old version of the plugin looked horrible (due to gradually loading of css, lack of png transparency support, border around nav images, doubled vertical space, etc.) - > broke the theme work Bob did? The UI properties were already gone when I submitted my patches, and the css support was only helping in replacing them. Is this the theme work you was referring to? > jvz. fabrizio
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
