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.
I'd like to chime in here with my +1.
I imagine maintaining three separate-but-similar component sets is quite a bit of work and, from what I can tell with the JSF 2.0, there will be enough major differences in the programming model to make backwards compatibility quite a chore (as Jesse noted). Merging the three sets would be difficult, so then why not try for a new set that takes all the best parts and is built "from the ground up" to leverage the JSF 2.0 programming model and concepts? It would not preclude Tomahawk, Tobago et al from moving to JSF 2.0 if that is the choice, but at the same time it would provide a fresh, unified JSF 2.0 component set that isn't hamstrung by backwards compatibility concerns and could move in its own direction if need be.
On a related note, what is the status of MyFaces and JSF 2.0? Is there any interest yet in creating a branch and "skeletoning" an implementation as the draft is released/updated? This is an area I'm interested in pursuing and would offer some effort if the community is interested.
Curtiss Howard
