You are technically correct on these points but the goals as stated in my post are to make a clean break with prototype.
On Sep 10, 2013, at 3:40 PM, "Thiago H de Paula Figueiredo" <thiag...@gmail.com> wrote: > On Tue, 10 Sep 2013 16:08:53 -0300, Lenny Primak <lpri...@hope.nyc.ny.us> > wrote: > >> Hi guys, > > Hi! > >> All JavaScript basically had to be rewritten nearly from scratch (see below) > > Rewritten from scratch just because you wanted to convert you existing > JavaScript code from Prototype to jQuery. Otherwise, you wouldn't need to > change anything (if still using the deprecated addScript() method) or a > little bit (to convert to Require.js modules and JavaScriptSupport.require()). > >> Assets in any library were moved into META-INF/assets, assets in the apps >> themselves can be left alone in the context where they usually are. >> CSS styles are now handled by bootstrap. Since tapestry.css is no longer >> there, anything that depends on those styles is broken. Also all bean editor >> based forms are broken due to these styles (see below). Right now this isn't >> fixed by core tapestry. > > Have you tried copying the 5.3 tapestry.css and adding it? I'm not sure it > would work 100%, but I guess it would at least speed up the fix. > >> The "core" stack isn't included by default, so unless you have t:alert >> component on your page, most styles won't be included and most assets will >> be missing from the web page. > > Yep, that's a little bit confusing, but I actually like this. Nothing needing > JavaScript, no JavaScript added. Of course, you can add @Import(stack = > "core") to your Layout component and fix the problem quickly. > >> - JavaScript >> Since there is completely new tapestry infrastructure and lack of prototype >> et all, >> None of the JavaScript remains compatible. > > I'm sorry, but this isn't true at all. There's no lack of Prototype.js. Just > set the symbol SymbolConstants.JAVASCRIPT_INFRASTRUCTURE_PROVIDER to > "prototype" and it'll be there. Actually, in 5.4, the default is Prototype > for compatibility reasons. Check the source of > JavaScriptModule.setupBaseModules() for more details. > >> Tapestry namespace is gone, as well as addScript interface, ZoneManager, >> pretty much everything. > > JavaScriptSupport.addScript() is deprecated, still exists and still can be > used. That's why I'm saying all existing JavaScript should still work > unchanged, at least in theory. I haven't tried that, though. > > -- > 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
