and what stoping u, to use yui? Ivan Nastyukhin [email protected]
On Jul 2, 2010, at 2:27 PM, [email protected] wrote: > Hi, > > Just a comment. > > I just had a brief look at rails.js (latest Rails 3 master) and > immediately noticed some really ugly errors like an accidental global > variable (no "var" statement for it) and re-declaration of variables > (more than one "var" statement for the same variable in the same > function), not to mention several forrgotten line-ending semi-colons. > Sure, it _works_, but would it be too much to ask to put such > "official" framework JS files, which thousands of people end up using, > through something like jslint(.com) for at least some basic syntax > checks? > > Also, is there a higher-level description of the intentions behind the > JS infrastructure? I've been a little reluctant to start working on it > from just the sources. Okay, it really isn't very complicated, but > addinng/chaning something is easier when one knows the intentions of > those who designed that stuff :-) For example, I don't know > immediately know what's there to support legacy code, nor what > features are supposed to be implemented by the "modern" JS > infrastructure. To me "modern" means all JS code is in .js files, and > data between server and browser is transferred using JSON(P) or XML, > but no inline-eval of JS code received through an XHR request (evil!) > nor of HTML. It's not obvious if my idea is the same as that of the > Rails development team, or if they/you take a more pragmatical view(?) > and also want to support those last two things as part of the "modern" > Rails 3 JS infrastructure, and not just for legacy support. > > Anyway, in general I haven't heard/read much about the JS stuff in > Rails 3 after some initial general announcements, while one can read > so much more about the Rails 3 mailer, router, activemodel, query > builder - the "core" Rails stuff. The JS infrastructure does not seem > to get all that much attention(???). > > Thanks. > > > PS: I would like to add YUI3 support (meaning "I'd like to DO it", and > not "I'd like to ask for it"). I would not bother with supporting the > inline legacy JS code and helpers though. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
