I need one of those. Which one should I choose? Mootools is attractive because has a nice effect library similar to scriptaculus but with better documentation. What do you think? --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Prototype :) On 3/12/07, Seth Illgard <Seth.Illgard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > > I need one of those. Which one should I choose? > > Mootools is attractive because has a nice effect library similar to > scriptaculus but with better documentation. > > What do you think? > > > > >--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
But why? Why prototype is THAT better? Doesn´t mootools has all the functions and classes that prototype has? Thanks On 11 mar, 16:03, "Gareth Evans" <agr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Prototype :) > > On 3/12/07, Seth Illgard <Seth.Illg...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > I need one of those. Which one should I choose? > > > Mootools is attractive because has a nice effect library similar to > > scriptaculus but with better documentation. > > > What do you think?--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Seth Illgard wrote:> But why? Why prototype is THAT better? Doesn´t mootools has all the > functions and classes that prototype has?Unlike a server-side library, JavaScript libraries are dreadfully hard to mix-and-match. Prototype''s name derives from how it attaches prototypical methods to pre-existing JavaScript objects. Any other library which does that will conflict with Prototype, so there''s generally only enough room in the hen house for one rooster. Next, Ruby on Rails wraps Prototype. So the checklist of benefits for Prototype must include a state-of-the-art full-stack web platform written in a fully OO language that makes very hard effects extremely easy to code. If you don''t need a web platform, and if some other library has the features you need, by all means use it. -- Phlip http://www.greencheese.us/ZeekLand <-- NOT a blog!!! --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Thanks a lot. Im nt planning to use ruby or rails in my CMS so....I think I have no reason to use prototype. I think ill stick with mootools for a while and see how does it works. If i get unhapy, ill test prototype. Thanks for the help. On 11 mar, 16:58, "Phlip" <phlip2...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Seth Illgard wrote: > > But why? Why prototype is THAT better? Doesn´t mootools has all the > > functions and classes that prototype has? > > Unlike a server-side library, JavaScript libraries are dreadfully hard to > mix-and-match. Prototype''s name derives from how it attaches prototypical > methods to pre-existing JavaScript objects. Any other library which does > that will conflict with Prototype, so there''s generally only enough room in > the hen house for one rooster. > > Next, Ruby on Rails wraps Prototype. So the checklist of benefits for > Prototype must include a state-of-the-art full-stack web platform written in > a fully OO language that makes very hard effects extremely easy to code. > > If you don''t need a web platform, and if some other library has the features > you need, by all means use it. > > -- > Phlip > http://www.greencheese.us/ZeekLand<-- NOT a blog!!!--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---