Hey, I introduced three "helper" methods to shared's HtmlRenderer (renderId(), getClientId(), shouldRender()). These methods are taken CoreRenderer (Apache Trinidad Podling).
I "ported" some Renderer's to use renderId() instead of using rw.writeAttribute(...) I figured out, that some Renderer's extend JSF' Renderer and some HtmlRenderer. I think we should define a clear "rule" on what base_clazz we should build our custom stuff. Trinidad's CoreRenderer and XhtmlRenderer (extends CoreRenderer) look interesting. Maybe these clazzes (or at least some methods) can be used for the *base renderer class* ? Can also be interesting for the Tobago Renderers. Also I (my personal thing) don't like static helper methods like DamnUtil.doSomething(). I like a more OO-based design. I think we should try to get rid of RendererUtils and introduce (step-by-step) its methods to the base_renderer_clazz; again XhtmlRenderer and CoreRenderer look promissing. WDYT ? -Matthias -- Matthias Wessendorf further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
