Comments

  1. January 15, 2009 at 2:49 pm |
  2. Kantra:

    Thank you for the great article, Ryan!
    Moo.RD is really, really powerful and highly extensible, i like it more than others mootools plug-ins and i’ve used it in many situations —
    What’s your favourite Moo.RD plug-in?

    Kantra

    January 30, 2009 at 11:10 am |
  3. Kantra:

    Sorry, the submit button treated me, i missed: “my favourite’s Moo.RD plug-in is Fx.Cycles.fadeZoom”. I agree with you considerations, the modular structure of mootools allows the creation of many extensions that can be as modular as they too.

    Sorry again for the double comment.

    Kantra

    January 30, 2009 at 11:18 am |
  4. adam:

    Hi Ryan,
    i also agree with your considerations, but it’s not the Mootools philosopy, this is the OOP philosopy. It’s main goal is to provide an highly reusable code, and Mootools, like a lot of other applications, implements this concept.

    A little consideration about the (great) Moo.rd library.
    Although i’m not a complete Mootooler (i use also others frameworks) my opinion about Moo.rd is quite simple: it’s a very good piece of code, the only Mootools extension i’ve ever used.

    However, when you said: “I don’t know what kind of coverage Moo.rd has across the web of Mootoolers…” i can reply saying it seems that the Mootools Team tends to stay away from Moo.rd, maybe because it’s so good and popular. I find a lot of material about Moo.rd around the Web, like articles, tutorials, etc, but there’s no mention about it in the ‘mootools extensions’ chapter of the Mootools Official Book i’ve recenlty read… very strange.

    Other frameworks tends to integrate themselves with the high-quality plug-in extensions developed by developers (i.e. jQuery UI) and this is a good practice, that respond to the question you asked in the article.

    January 30, 2009 at 5:35 pm |

Leave a Reply

You must be logged in to post a comment.