I think you may be underestimating the value of the ecosystem around the core Tapestry 5. By now, there are lots of well supported libraries that are commonly used in Tapestry 5 projects. All in all, just missing the Tapestry and T5 namespaces on the client doesn't look all that bad to me but I think we could greatly ease the pains of community upgrading with a long alpha cycle with public releases and actively encouraging and helping the library developers to upgrade their libraries to 5.4 before a GA release.
Kalle On Fri, Oct 19, 2012 at 4:41 PM, Howard Lewis Ship <[email protected]> wrote: > I you've seen the commits, you know I've been attacking the > client-side JavaScript with a chainsaw. Not everything is working, > especially the tests (!), but what does work is kicking ass. > > However, maintaining backwards compatibility is proving to be a huge > challenge. > > Keeping all the components working is not going to be that hard; > neither will making them work with either foundation (Prototype or > jQuery). > > What is going to be increasingly hard to keeping the Tapestry and T5 > namespaces working the same as before. > > So the question is ... what are the downsides of just ignoring > compatibility? Again, this is strictly on the client side, and > relates to all the effectively un-documented JavaScript code scattered > about in the existing tapestry.js and t5-*.js libraries. > > I know this will affect my applications a bit; it means that 5.4 will > be a more difficult transition as my code has a lot of patches around > T5 limitations. Even so, I suspect it will be just a matter of a > couple of days to upgrade the existing app. > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
