pepe wrote: [...] > Very true, that's why I mentioned Rails generated JS because you don't > actually need to know JS to start using it if you let Rails generate > it for you.
No! That will only land you in trouble without you knowing enough JS to get *out* of trouble. You have to understand what Rails is producing. > True, as Marnen mentioned the generated code is not really > pretty, but it works It's not about pretty. It's about proper architecture. Inline JS is improper architecture. > and if you ask a boss or customer what is that > they prefer, pretty vs. working code, I can tell you that not 100 but > 200% of them will choose working. ;) I don't give my clients that choice. They get properly designed code that works. It's not up to the client to make technical decisions. > > The good thing about Rails generated JS is that there are good > tutorials and books. I personally love the Ajax on Rails book by > O'Reilly, if it's of any use to the OP. What's so hard about learning JavaScript? Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
