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]
