MoonKiKi: web2.0 and ajax... the evolution road

Tuesday, February 3, 2009

Happy MOO Year

We are thinking the same: this will be the Moo Year.

Today the great news (they posted it before in clientcide), but now it's official, we are waiting for the MooTools 1.3:


2009, The Year of the Cow - What’s Coming with MooTools

Written By Aaron Newton, on Monday, February 2nd 2009, 8:51pm

Ok, it’s the year of the Ox, but you get the idea. Regardless, it’s shaping up to be a very interesting one for MooTools. There are many things going on with the framework and we thought we’d give you a heads up on what you should expect in the coming weeks and months.

MooTools 1.3

As discussed elsewhere MooTools 1.3 is on the horizon and features numerous changes that will interest you. The caveate here is that all of this is subject to change, as the work is still very much underway.

  1. Class is getting a rewrite that should make it both less likely to encounter browser issues but will also empower you to do some cool stuff like post- and pre-initilization mutators and inherit object properties from prototypes (the current Class breaks this inheritance link for things like options to prevent pollution across instances).
  2. There is a new Type constructor that has numerous methods that help you manage objects. For instance, the $type method is now Type.of and there are methods for each type (Type.isString(‘foo’) === true). In addition, most Native instances will have a .from method (Array.from(iterable)).
  3. Most of the $method functions are moving into better places in the framework. This means that $type is now Type.of, $emptyis Function.empty, $lambda is Function.lambda, $random becomes Number.random, etc. Not all the $methods will get this treatment as there are at least a few of them that don’t really go anywhere. We’re still discussing what to do with them ($pick, $each, $defined, etc).
  4. Event Delegation will make it’s way officially into the framework (there are some implementations out there of this already).
  5. Hash, Cookie, and Swiff are all likely moving into mootools-more. The thinking here is that the Core doesn’t need these things to function and while they are useful features of MooTools, they aren’t needed by everyone.
  6. In a new policy change, the default pre-built version of the MooTools core will come with the compatibility layer for the previous version built in. This means that if you have a site running MooTools 1.2 you should be able to just drop in 1.3 and continue partying. You’ll want to start using the MooTools 1.3 syntax going forward, but in general, upgrading should be a loteasier.
  7. Various small bug fixes and the like.

Read the entire news on MooTools' blog

No comments:

Post a Comment