Alexandre Poitras wrote:
I agree with you Michael since our designer is a big fan of Zen Garden
and I must say I don't miss working with tables :) I would like a
strict XHTML rendererkit but I must say that at least the JSF standard
components don't produce garbage . What I am doing right now is
developping new renderers for the components I need, it doesn't take a
big effort anyway. Maybe I can regroup those renderer in a rendererkit
once I have several renderers done. But it's the main weakness of a
Hint, you could donate it to myfaces ;-)
component approach, having to deal with the generation of markup that
maybe you don't like. But at least in JSF the renderer is separated
from the UI component.
yes one big plus of myfaces is this separation, it is one of the points
which makes the component programming really awkward at the first sight
(the other one being the taglib docking code), but it is not like
you develop components every day, due to the fact there already are so
many of them.
This separation in the first place between taglib code, view logic and
controller logic on component level with xml as binding in between is
awkward, but if you need special cases then it is rather "easy" to
adjust those to your needs without breaking existing code.
The component api definitely at first sight is hell to program for in
JSF, but for easy on program componentization there already are easier
solutions like shale clay, facelets, aliasbeans etc...
but in the end it pays off if you need special cases like this one.
(Hint the component api itself is one of the major gripes I still have
with JSF, it only can become better)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
