Please quote when replying. Ants Pants wrote in post #973055: > Why?! Well, Prototype was great to get up and started and do fancy > things, > but then when I wanted to know how things worked or have more control, I > found I didn't know how to.
RTFM? > Having a method that you pass arguments to > is > great but it isn't enough. Huh? I'm not sure what you mean by this. > > JQuery is a steeper learning curve but you have more control, your > javascript is in js files and not sprinkled around your HTML You can do that with any JS framework, or with none. And you should -- JS doesn't ever belong in HTML. I'm not a Prototype supporter as such, but your reasons for not using it seem pretty specious. > and you > actually learn more about the front end. So, I'll ask again: what properties *of the jQuery framework* make it superior to Prototype in your opinion. > > I'm a backend developer and hate the front end but it has been kind of > fun > (but stressful and frustrating) and I have learned heaps. > > That's why. but I guess it horses for courses. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] Sent from my iPhone -- 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 [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.
