Thanks for the quick response Howard. Your comment on the DTD sounds spot on and I didn't consider that (probably the most obvious thing) earlier today. The framework is pretty ancient compared to what's currently vogue, but our Tapestry 4 application is a mature product that has established a strong position in the market and has a solid revenue stream, so it certainly does it's job. As I understand, upgrading to Tapestry 5 from 4 is not the simplest of tasks, so it would be difficult to approach the business highlighting the fact that we have technical debt and wish to progress to "yet another framework", which will probably have the same issues 5 years (1 year web time..) down the line.
I believe keeping up with technologies (even more so in the domain of web development) is beneficial from a technical standpoint, but If I need to bin a framework in favour of what is currently vogue in the market, which (from the point of view of the business) brings no additional revenue in, then I've going to have a tough battle with management. It's a sad fact that we are dominated by deadlines and limited budgets and somewhere in between, we (technical folk) are trying to make the best product we can :) I doubt there is any flaws in Tapestry 4, I just thought I'd run this past the forum before doing any further investigations. I'll take a look tomorrow and if I find anything, I'll update the post. Thanks again for the promptly reply and suggestions! -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-4-chrome-support-tp5615994p5616198.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
