Phani wrote:
Thanks Eric for your detailed explanation. Even I got confused of which one to take i.e Mootools or Prorotype. But your explanation above could well help me in deciding.
Eric says: "Prototype has more of a 'Improve The Javascript Language' approach." he should probably have said: "Prototype tries to make javascript look like another language." The most valuable contribution of Prototype-like frameworks is the hiding of browser vagaries. You should also search for discussions of what's not to like in various libraries, don't just listen to the good side.
One thing which I still wanted to learn is the basics of OO in JS, without which its impossible to understand the code written behind it.
An epiphany! Yes, learn the underlying language thoroughly otherwise you will never know what is happening "under the covers", regardless of the library you use.
Could you let me know the good resource which would help me in understanding the concepts better.
An excellent idea: <URL: http://www.crockford.com/javascript/ > A general resource: <URL: http://www.jibbering.com/faq/#FAQ3_2 > -- Fred --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
