I try and stay current since upgrades have been mostly painless. In fact so far it's been 3rd party library upgrades such as Hibernate that have caused me the most problems. I guess the Hibernate one was necessary and now it looks like Prototype might introduce issues so I'll throw on my 2 cents.
I have plenty of Prototype code but all my new development is jQuery. If I start a new project I turn Prototype off. If I have to work on older Prototype code I generally just convert it to jQuery. So my personal preference would be to leave the Prototype version alone because apparently if I upgrade to 5.3.5 I'm going to need to retest and possibly fix/convert old code. So my vote would be to never update Prototype. I realize my situation might be unique but I figured I'd just throw it out there. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Re-Tapestry-5-3-5-BACK-OUT-Prototype-1-7-1-tp5716095p5716117.html Sent from the Tapestry - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
