I believe if you keep prototype, there is a compatibility module that keeps that namespace. I am not 100% sure about that because I never tested that scenario.
On Sep 11, 2013, at 11:34 AM, Norman Franke <nor...@myasd.com> wrote: > What about the missing Zone Manager? I have a number of scripts that need > that. If it's missing, then he is partially correct in that a good deal of > things will need to be re-written. > > Norman Franke > Answering Service for Directors, Inc. > www.myasd.com > > > > On Sep 10, 2013, at 6:57 PM, Thiago H de Paula Figueiredo > <thiag...@gmail.com> wrote: > >> On Tue, 10 Sep 2013 18:35:07 -0300, Lenny Primak <lpri...@hope.nyc.ny.us> >> wrote: >> >>> You are technically correct on these points but the goals as stated in my >>> post are to make a clean break with prototype. >> >> Agreed, but the way you wrote your e-mail it seemed that everything in >> JavaScript needed to be rewritten from scratch because of the Tapestry >> upgrade, something which isn't true, because most of the rewriting you did >> was because you switched from Prototype and jQuery. You also said that >> Tapestry 5.4 didn't include Prototype.js [1] and that >> JavaScriptSupport.addScript() doesn't exist anymore [2], both statements >> completely wrong. Not using them doesn't mean that Tapestry don't provide >> them anymore. >> >> I'm just trying to calm down anyone who wants to upgrade from 5.2 or 5.3 to >> 5.4 in the future and telling them they will *not* need to rewrite all >> JavaScript from scratch, something that could be implied from your e-mail. >> Just the parts that use code from tapestry.js like the T5 namespace and >> stuff like ZoneManager will need to be rewritten. >> >> Backward compatibility is a very sensitive subject for Tapestry due to >> historical reasons we just can't ignore. >> >> [1]: "there is completely new tapestry infrastructure and lack of prototype >> et all, None of the JavaScript remains compatible." >> >> [2]: "Tapestry namespace is gone, as well as addScript interface" (in this >> sentence, the Tapestry namespace is actually gone, but >> JavaScriptSupport.addScript() is still present and working). >> >> -- >> Thiago H. de Paula Figueiredo >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
