+0
While I see the merit of starting over (and certainly wouldn't argue
against a new component set based off of 2.0), I don't think we should
abadon/restrict renderkits from continuing to support emerging
standards. I know that many of the folks on Trinidad are interested in
supporting 2.0 going forward and I would suspect the other renderkits
are as well.
Scott
Jesse Alexander (KSFH 323) wrote:
I am wondering whether the event of JSF 2.0 would not be a good
moment to create a new component set.
Well... another component set?
The main thoughts behind it are
- the 3 MyFaces component sets
- are somewhat incompatible
- have each their good points
- have some weak points
- are missing some "cool" components
- partially have duplicated components
- are partially missing important concepts
JSF 2.0 brings a new concept to do components.
Now it would be possible to update each component set to JSF 2.0...
but a Tomahawk/JSF2 is "expected" to be backward compatible. So it
would be difficult to radically change components or eliminate some
duplicates...
Whereas a new component set that would
- take all good concepts from the existing 3 component sets
(and maybe some more from other comp-sets?)
- deliver a clean set of components
- just do it for JSF 2.0
- not have to take backwards compatibility into consideration
I think if such a new component set would fit, then it would be now the
right time to think about the requirements... and as soon as a
workable beta is around the first steps for the realization could be
made...
regards
Alexander
