2011/3/3 françois facon <[email protected]>: > seems to be compatible with jQuery and others toolkits. > better performance on both client an server side. it's Green. > +1 for tapestry-minification, or 3rd party library (in case license trouble) > Perhaps this will also let the door open to use any compressor during the > Maven *build.* >
I think the advantage of doing it at runtime, rather than build time, is that the un-minified files are always there, which are easier to debug on the client. I think it's a have-your-cake-and-eat-it-too situation ... though there's the cost of aggregating and mini-fying the JS files the first time. Other solutions involve shipping multiple copies of files (individual, minified, aggregated, aggregated/minified). That can cause its own problems, not just bloat. > 2011/3/3 Howard Lewis Ship <[email protected]> > >> Check out my most recent commit, which will make it super-easy to >> override any default behavior. >> >> On Thu, Mar 3, 2011 at 11:09 AM, Josh Canfield <[email protected]> >> wrote: >> >> So ... where should the hooks into YUICompressor go? Could put it >> >> right into tapestry-core, could create a new sub-project, >> >> tapestry-minification, or it could just be a 3rd party library on >> >> GitHub. >> > >> > I would make my decision based on whether this would turn into a >> > prototype vs. jquery debate at some point. If you make it a module >> > then I assume core would get public APIs that would make integrating >> > the next great js/css compressor. >> > >> > Maybe just keeping an eye on replaceability would be good enough. >> > >> > Josh >> > >> > On Thu, Mar 3, 2011 at 10:16 AM, Howard Lewis Ship <[email protected]> >> wrote: >> >> If you've been watching the commits, I've been reorganizing things >> >> inside Tapestry's asset processing to support some new features. The >> >> big goal is JavaScript (and CSS) minification. Right now, all the >> >> pipelines are in place, and there's a placeholder service, >> >> ResourceMinimizer, waiting for a real implementation. >> >> >> >> I've targeted YUICompressor >> >> (http://developer.yahoo.com/yui/compressor/) which uses a BSD license >> >> (and requires Rhino, MPL license). I believe these are compatible >> >> licences w/ ASL. >> >> >> >> So ... where should the hooks into YUICompressor go? Could put it >> >> right into tapestry-core, could create a new sub-project, >> >> tapestry-minification, or it could just be a 3rd party library on >> >> GitHub. >> >> >> >> Thoughts? Preferences? >> >> >> >> -- >> >> 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 >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> >> >> > >> > --------------------------------------------------------------------- >> > 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 >> >> --------------------------------------------------------------------- >> 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
