Am 19.02.2007 um 04:34 schrieb Colin Mollenhour:
> If you are going to do any *serious* Ajax work you are going to > need to know Javascript, unless you limit yourself to whatever > frameworks out there provide to you, which currently isn't much. I disagree. With Rails RJS templates, you can code _very_ complex Ajax-powered apps, without having to know JavaScript. Personally, I use it a lot (note you can also mix-in your hand- written JS if you want to!). The best thing about on-demand JavaScript generation on the server is that the control over the view is not split-up between client and server but rests firmly with the server, where your MVC (or other) framework sits. This equates to _much_ less cruft, by having to write no or less code that ties server and client together (think spitting out data on the server and parsing that in JS). Check out the cheatsheet: http://slash7.com/assets/2006/10/8/RJS-Demistified_Amy-Hoy-slash7_1.pdf Note that there is other stuff out there that relies on code generation, too (like the Google Web Toolkit, which I haven't used but I'm pretty sure you can do *serious* stuff with, like with RJS templates+Prototype). Mind that it doesn't save you from knowing what's going on in the DOM and what Ajax can and cannot do-- it just means you don't have to get into the innards of JavaScript if you don't want to. :) Of course, code generation limits you, but that isn't automatically a bad thing. Many great real-world sites use it all the time. YMMV. Best, Thomas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
