On Sun, Dec 2, 2012 at 7:51 AM, Serge Eby <[email protected]> wrote: > Hi, > > Disclaimer: T5.4 is still work in progress, so this is just to provide an > initial feedback of my experience upgrading a small pet project from T5.3.6 > to T5.4. > > Overall, the upgrade was smooth. I am building the Jars locally while > skipping the tests as I know things are still in flux. I just wanted to get > a feel of how much effort will be needed and how to leverage the new > features. > > 1) I removed all references to my custom Twitter Bootstrap integration and > use the following on my Layout class: > > @Import(stack = {"core"}, > stylesheet = {"context:css/custom.css", > "${tapestry.bootstrap-root}/css/bootstrap-responsive.css"} > ) > public class Layout { > > ... > > void afterRender() { > javaScriptSupport.require("bootstrap"); > } > } > > 2) I added to following to AppModule ApplicationDefaults configuration > > configuration.add(SymbolConstants.COMBINE_SCRIPTS, "true"); > > This is just to minimize the number of javascript files to load. > > This is the default in production mode; your contribution means it occurs in both production and development. This really hasn't changed from 5.3.
> > The above 2 changes were enough to get me going. Note that I don't have a > lot of custom JavaScripts in this project, so YMMV. > > I ran into a few issues: > a. I still see Prototype & Scriptaculous (+t5.3-compatibility) being > loaded. > How can I get rid of these completely without overriding the core > JavascriptStack? It appears that there is some conflict between Prototype > and JQuery causing the collapsing responsive navbar not to properly > function. > I suspect more people will be using one or the other, not both (i.e. JQuery > vs. Prototype), therefore an easy way to pick and choose would be nice. > > Pure jQuery mode is coming, after I merge back into master. I'm not quite certain what you'll configure ... probably a symbol. > b. When using any app context other than "/", the assets URLs are > incorrect, > therefore Bootstrap not properly loaded. Do I need a configuration for > this? > I noticed the change in tapestry.asset-path-prefix in the release notes, > but > not sure if this is causing some problems. > This needs some investigation. I think there are tests failing because of this already. > > > That's it for now... > > Thanks and looking forward to the official alpha release! > > Having trouble scraping together hours to work on this ... but that's because I'm busy on projects. > > /Serge > > > > -- > View this message in context: > http://tapestry-users.832.n2.nabble.com/T5-4-First-impressions-tp7583860.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
