I'm differently against SPI and all that javascript abstraction. In my opinion, if you write javascript clean:
use coffeescript separate different functionality into own files no .ajax, console. wrappers use provided framework functionality if you need to acknowledge an error throw an exception eliminate dependencies by using events as the API between them … final result is that you have pretty manageable javascript and if you don't like the framework you can easily rewrite it or just copy and extend it, in big projects it is probably needed anyway. I'm for as less javascript as possible solution and jQuery. Denis 25. 10. 2012 v 23:28, Howard Lewis Ship <[email protected]>: > As much fun as I've been having with the JavaScript abstraction layer > ... is it really needed? > > Could we please 90% (99% ?) of our users by providing jQuery out of > the box, and coding the Tapestry support directly against it? > > How many people will care about the SPI? How many will stay on > Prototype when jQuery is an option? How many will be desperate top > use just MooTools. or just YUI, or just Dojo, and can't handle having > anything else? > > Just want to explore all the options. > > -- > 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]
