Wednesday, January 31st, 2007

Mootools 1.0 Announced

Category: Announcements, JavaScript, Library, Toolkit

<p>Mootools 1.0 was officially announced to the world.

Big Changes

  • All the MooTools Classes use now Events. No, not element events. Class Events. Right, you can add as many onCompletes as you want, onChange(s), onStart(s).. Well, you get the idea. Options starting with “on” become events, so need to change your code on this one.
  • All the code, plugins, everything now uses element events. With a completely rewritten event system, its now less memory hungry and a whole lot easier to add events to your elements. You wont find another .onclick in MooTools. We’ve also added the ability to fire an event by hand, or remove all of the events from an element, or all of the events of a certain type (ex. click).
  • There are also a number of new “Components”, like Color, to convert colors from HSB to RGB and vice-versa, Hash, to create more flexible javascript objects.
  • New plugins have been added, like SmoothScroll, the Scroller, Slider, Assets and Json.Remote, to make Ajax requests directly with Javascript objects. As always, you decide which components to include, so your own version wont be bloated.
  • Effects are now more powerful than ever, Fx.Style/Styles/Elements now can include colors and shorthand properties. They also support one value start (the starting value will be computed in real time). You have a div with height = 100 and want to go to 200? as easy as start(200). Fx will read your current style.

Read more

Any Mootools users out there? (I know there are). What do you like about it? What made you choose it as your library of choice?

Mootools

Related Content:

Posted by Dion Almaer at 12:30 am
19 Comments

++++-
4.6 rating from 69 votes

19 Comments »

Comments feed TrackBack URI

SmoothGallery (http://smoothgallery.jondesign.net/) uses Mootools and is a very handy tool indeed. Besides that, I’d never heard of it.

Comment by Sean — January 31, 2007

If u want to get startet with mootools, here is the official beginners guide:
http://clientside.cnet.com/wiki/mootorial

I started with mootools some time ago and work with 1.0 since its in development, i love it. Smooth effects, clean code, best framework i ever used. If u want a modular framework with minimal size and full of nice features, u need mootools ;)

Comment by digitarald — January 31, 2007

Recently I started using Prototype for a new project, but started looking for an alternative pretty soon: the size of Prototype 1.0, 70kb, is really large for a JavaScript library that does not even have widgets or effects. The best compressor I found reduced it to 38kb IIRC, but still… I also noticed that on computers in the 1 Ghz range the loading and parsing of Prototype caused a noticable and somewhat annoying delay every time a page was loaded – even when the page was stored locally.

So I looked for an alternative and found mootools. Thanks to the modular download I could easily create a small and compressed version. So now I am down to 13 kb, and the delay is gone. Even though I miss a few Prototype features (especially the onFailure event in Ajax), I am happy overall.

Comment by Tim Jansen — January 31, 2007

I use it on my site http://www.stage.fm/ for things like drop down search menus, sortables, and severial custom apps. It is great, it provides a clear OO syntax (like Dean Edwards base.js) and most of prototype’s functionality, but without the bloat. (Not to say that prototype is extremely bloated) The backend is done in rails and I am working on creating moo bindings for all of the prototype helpers in rails.

Comment by Ryan — January 31, 2007

Even though I miss a few Prototype features (especially the onFailure event in Ajax)


//sending a XMLHTTPRequest
var testXHR = new XHR(
{
method: 'get',
onSucces: showSucces,
onFailure: showFailure,
}).send('http://example.com/script.php','mootools=wicked_cool&favorite=solutoire.com');

Comment by Teun — January 31, 2007

I started off with moo.fx, mootools’s predecessor, because it was the easiest/lightest way to do simple transitions I could find. Then it added a lightweight XHR class, which also made life easier, and so on…

Comment by Chris — January 31, 2007

yay! about time a final release came out — I love this little engine. but… the documentation for Tips.js stinks! :P

Comment by mdm-adph — January 31, 2007

Been using moo in projects for the past year. Moo is one of those things that you would code if you had the time – it really is elegant code.

Comment by Karl — January 31, 2007

Moo rocks

Comment by Dan — January 31, 2007

Been using it on an intranet but pretty soon I will be releasing two or three public sites with moo.

Comment by Klaus — January 31, 2007

It’s really lightweight and efficient. I just wish they had better demos and example code. They used to but they disappeared for some strange reason.

Comment by markus941 — January 31, 2007

Does this version have something similar to Prototype’s onLoading = function option for the ajax class? It’s the only thing miss from Prototype.

Comment by Andrew warner — January 31, 2007

I’ve been using mootools for quite some time now and must say the biggest draw for me is the inclusion of the penner easing equations. The FX library is incredibly solid, doesn’t require div-itis, and uses the same physics easing equations as most flash users. Also, the incredibly small size and built in compression/obfuscation is invaluable.

Comment by Sean Madde — January 31, 2007

This is the first time I’ve heard of the advantages of Class events over element events. It does make some sense though. Why aren’t other frameworks going in that direction? Just wondering what the drawbacks are to this approach.

Comment by Dan Kubb — January 31, 2007

One more shout out for mootools here! I started with Protaculous as well, and don’t have anything bad to say about it, but it does seem that moo can do pretty much the same things with less code.

Comment by Mike Ritchie — January 31, 2007

Ease of use and elegant design.

Let this mark the death of flash.

So it is written.

So it is done.

Comment by Karl — January 31, 2007

Moo!

Comment by Somebody Else — February 1, 2007

Started with moo.fx and have loved it every step of the way. Great, elegant code. Easy to use, easy to learn.

Comment by Tim — February 1, 2007

I’ve been a frequent prototype user but recently switched over to mootools and never looked back. In comparison to prototype/scriptaculous mootools offers cleaner, easier to understand code in a way smaller library (filesize wise) and has great documentation.

The new prototype website offers some great documentation on that library too but that’s too little too late … i’m a moo fan now!

Moo!

Comment by Chris R. — February 8, 2007

Leave a comment

You must be logged in to post a comment.