nilo de roock <ndroock1 <at> gmail.com> writes: > I don't know if the license permits, but I really hope Tapestry 4.1 will be > forked. The ideas in 5 are really cool and could be used as a vision for > developing 4.2 but in a slower pace perhaps and without breaking code. Yes > it will be more difficult, so what?
The idea that T5 is coming too soon and existing code won't work in it sounds like a valid concern. However, if you think more about it, you may just hold off upgrading and wait until T5.1/T6 when you have received enough return on your investment on T3/T4 or when you start a new project? If there are enough people facing situations like you, then there will be a critical mass to maintain T4. The idea of creating a runtime compatibility layer sounds like an excellent idea. However, if you think more about it, given a working T4 applications, what do you gain by running it on this compatibility layer in T5? Instead, I think a better thing to do is to target those who are upgrading an existing T4 app to T5. 1) Create a migration tool that can automatically convert the source files to T5. It doesn't have to work 100% accurately, but should do the bulk of repetitive work in some limited scopes. 2) Create a platform that allows T4 pages and T5 pages running in the same app and create a bridge to allow them to communicate or to share ASO. -- Kent Tong Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
