On Thu, Oct 25, 2012 at 3:06 PM, Denis Stepanov <[email protected]> wrote: > I'm differently against SPI and all that javascript abstraction. > > In my opinion, if you write javascript clean: > > use coffeescript
That is irrelevant, but I prefer coding in CoffeeScript. > separate different functionality into own files I thought you didn't like that? Yes, I'm doing many small modules. > no .ajax, console. wrappers use provided framework functionality I don't follow you here; the wrappers are there for a purpose, which is that the functionality does not always exist; if every bit of code that wanted to use the console was written for all the possibilities across browsers, it would be a disaster. Likewise, the Ajax abstraction are in two layers; 1 layer is the foundation framework (e.g., Prototype or jQuery). The other is extra reporting, and automatic handling of the partial page render response before giving control back to the success handler. > if you need to acknowledge an error throw an exception This will tend to make things very brittle I think, especially for apps that are hitting rough edges upgrading from 5.3 to 5.4. Maybe I'm falling into the old trap, though; I'll think about it. > eliminate dependencies by using events as the API between them This is certainly the case, and the events are well defined because there is a namespace just to define the events. > … > > 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. That is certainly the path we're on, in the 5.4-js-rewrite branch. > > I'm for as less javascript as possible solution and jQuery. I think the amount of JavaScript in 5.4, will be much smaller than 5.3, and accomplish a lot more. > > 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] > -- 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]
