Toluu : MooTools

MooTools - Home

The Blog

SizzleDecember 4 2008

During the last couple of days, there has been a discussion in various places about JavaScript frameworks implementing Sizzle, the new CSS selector engine by John Resig, which is allegedly the fastest.

Resig wrote Tom an email, saying that he would be pleased if MooTools joined the other frameworks by implementing Sizzle in its codebase, replacing our own selectors engine. I don’t really know how many frameworks are actually thinking of using Sizzle in place of their own selectors code, as the only source I can find for this is Ajaxian.

Their information about Dojo wasn’t correct, so I’m assuming that information about other frameworks is incorrect as well. I do know that Dojo is considering including Sizzle as part of the Dojo foundation, based on an email Dylan Schiemann wrote to Aaron Newton. As I understand it, Sizzle would become a Dojo Foundation project, with the ultimate goal of including it into Dojo Toolkit. They have this idea of having the major framework developers all contribute to a unified CSS selector engine.

Now that you know the general picture, let me explain why this is a bad idea not only fo

MooTools 1.2.1 ReleasedOctober 16 2008

In keeping with our new pledge to release more often, we’ve been working hard lately to get 1.2.1 ready for release, and we’re finally happy with it. This release brings a ton of bug fixes, and is a drop in replacement for 1.2.0. (That’s right, no breaking changes!)

What’s new?

Element.Properties.html (element.set('html', html);) now works even with select and table elements in Internet Explorer. Element:clone is also now faster than ever, and retains the values of form elements being cloned. A lot of work has also been done to fix some bugs in Class.js, and Safari 2 support is now back. With the help of Daniel Steigerwald, we’ve also cleaned up quite a few memory leaks in IE related to events and Element storage, and destroyed elements are now more effectively destroyed.

For a complete list of changes, see the changelog on GitHub…

What’s next?

We are going to keep going through all the tickets, and try to start fixing the bugs that have cropped up with some of the plugins. 1.2.2 might also see a few new features as we start preparing for some exciting changes and additions we have planned for 1.3.

MooTools 1.2 will be

What’s going on with MooToolsSeptember 23 2008

A very brief article to explain what’s happening in the world of MooTools, and provide users with some links so they can get further information if they feel they need it.

So, what the heck is going on

Recently, a few users have been concerned that newcomers to MooTools might not easily be able to find their way around the MooTools community. As one of the developers, I kind of disagree, but there is one thing I think we all agree on; It probably wouldn’t hurt for us to communicate with everyone a little better. ;)

Along with the 1.2 release, we’ve changed up the site and moved away from SVN development. We’ve also removed Trac and the official forum in exchange for GitHub, Lighthouse, Google Groups, and other MooTools user maintained forum solutions. There is a ton of reasoning behind all the outsourcing and changes (including the simpler site, removal of the forums, switch to git development, etc) and if you like, you can read more about them…

here
here (sorry I can’t count!)
and here

Is anyone actually writing any code?

Currently, we are working on getting the 1.2.1 release out as soon as possible. It focuses on bug fixe

Calling All PluginsJune 23 2008

One of the main things missing since the forums have gone into read only mode is the Your Scripts section. We realize this and are working to complete our own plugin directory.

We’re trying to assemble a comprehensive list of all our plugins. As part of this effort, we’re asking all plugin creators to send an email to plugins@mootools.net with the following information:

Plugin Name
Plugin URL
Plugin Description (one line)
Plugin author name and link (if applicable)

At this time, we’re only interested in collecting data on plugins which are compatible with the 1.2 release.

This is a temporary measure until we get a more interactive system in place.

MooTools 1.2: It’s Official!June 12 2008

I speak for everyone the MooTools team when I tell you that we are extremely happy to announce the official release of MooTools 1.2. After a year of development and six months in beta, you might call us perfectionists. But now we’re finally ready to call the 1.2 release complete and stable. For those of you who have been waiting to make the switch, now would be the perfect time.

Not only has the API been completely revamped, but there have been several significant changes to the site and the way the MooTools community interacts.

Why the Rush?

You may have noticed that the 1.2 release has come, quite literally, overnight. Over the past few months, we’ve come to realize that the 1.2 beta is even more stable than the “stable” 1.11 release. In fact, many developers (including some of us on the Moo team) have been using 1.2 in critical applications for some time now.

Users coming into #mootools asking for support have been unofficially told to by us to upgrade to 1.2 for months. Reluctant as we were to let ourselves call our work on 1.2 “complete”, the reality finally hit us that it was time to officially offer our release to the entire development community. We therefor decided to “just do it”, flipping the final switch and changing to the new version of the site before this blog post and some areas of the site were completely functional.

Toluu