On 19 Feb 2009, at 11:30, Greg Hauptmann wrote:
> Hi, > > Question - If I'm starting to use Rails javascript/ajax helpers but > want to start doing some more custom/complex Ajax/Javascript should > I learn RJS as part of moving forward? (or alternatively just look > to either diving into jQuery or Prototype/Scriptaculous?) > Personally I feel that rjs can be a bit of a crutch as there is only so much it can do (or some things that it doesn't do as well as using raw js). I found The prototype & scriptaculous book (Christophe Porteneuve) very useful, mainly because it showed me that javascript doesn't have to be horrible. It sort of depends what you're going to be doing really - you can probably carrying with rjs if you're just using the odd scriptaculous effect or ajax request, but you usually can do those things in a cleaner way with a bit more knowledge of JS. In my case we have quite a lot of javascript which would have been hellish (and hard to test) with rjs (we have a variety of javascript classes which encapsulate the behaviour of a particular 'widget' on the screen) Fred > Tks > > > > > -- > Greg > http://blog.gregnet.org/ > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 [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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
