Hi Andrew, Yes I think Adam made a wiki for UIXNode conversion during the time of incubation, I'll have to look for the link.
As for JSF 2.0 adoption, I would say 2 years after the specification release which is... not so soon. Implementation will start before that though and I think it's what important for our side. So personally I would say clean up the code... a lot as not only UIXNode need it, but wait for JSF 2.0 so that our cleaning reflect JSF 2.0 changes, but working in a 1.2 environment. I gully agree about 1.0 trunk, I have no motivation at all about it. Regards, ~ Simon On Mon, Sep 29, 2008 at 1:40 PM, Andrew Robinson < [EMAIL PROTECTED]> wrote: > > However, as Matthias pointed out, JSF 2.0 standardize Trinidad's > principal > > core features namely PPR and Resource handling and hopefully skinning > too. > > Under such circumstances, I feel that we should wait for 2.0 to be > cemented > > before going through a massive refactoring of some of the old and twisted > > code parts so that the refactored design is fully compatible with 1.2, > but > > using 2.0 concept to make the upgrade to 2.0 easier imho. > > Although those are really good concerns, I wonder how long it will > take JSF2 to be adopted. It seems like many are even reluctant to > adopt 1.2. So I wonder if it is still worth it for us to make an > effort to at least clean up the 1.2 trunk? (I did not mention the 1.0 > trunk as I seem to have lost my desire to maintain the JSF 1.1 code > myself) > > I guess it comes down to time and desire. I worry about the UIXNode > conversion as I don't yet fully understand that code enough to feel > comfortable porting it without missing things. I guess I could create > sandbox renderers for the components, then if they look complete, we > could promote them & replace the UIXNode ones at that time. Is there a > WIKI page that I missed that talks about how to convert these guys or > about any of the UIXNode architecture? > > -Andrew >
