Articles in the ‘Releases’ Category

MooTools Core 1.3 Stable and MooTools More 1.3RC

Written By Christoph Pojer, on Monday, October 11th 2010, 4:11pm

Good news, everyone! We are extremely happy to announce the official release of MooTools Core 1.3 after almost a year of development. You might call us perfectionists, but we’re now ready to call the 1.3 release complete and stable. For those of you who have been waiting to make the switch, now would be the perfect time. In addition, MooTools Core 1.3 is fully backwards compatible with all documented functionality of MooTools Core 1.2, but more on that later.


MooTools Core 1.2.5

Written By Djamil Legato, on Wednesday, September 15th 2010, 6:17pm

Today we’re releasing MooTools Core 1.2.5, which can be considered the last version of the 1.2 series. 1.2.5 is a maintenance release, and contains fixes for the latest beta browsers, such as Firefox 4 beta, Chrome 6 and IE9 beta. Below, a quick changelog:

  • Fix for fireEvent under IE9 beta.
  • Forcing MooTools bind implementation to work with the latest gecko / webkit beta browsers.
  • Fixes HTML Elements creation in IE9 beta.
  • Fixed Elements garbage collection in IE.

Or, if you prefer, you can have a look at the actual code diff.

Documentation has been updated accordingly and many new Specs have been added.

As usual, you can quickly download it or build your own version.

Keep an eye out for the 1.3 release in the following days!

MooTools More,

Written By Aaron Newton, on Tuesday, February 9th 2010, 9:10pm

UPDATE: is also released; there was a new bug in Tips introduced in that was immediately patched.

This is mostly a bug fix release.

  • Nearly 50 bug fixes (see the milestone for in Lighthouse).
  • Keyboard:
    • Added some support for just pressing ‘shift’, ‘control’, or ‘alt’
    • Added a bunch of keycodes for Mac compatibility
  • Keyboard.Extras:
    • Support for “shortcuts” which are keyboard entries that have names and descriptions.
    • Also provides methods for listing all the active shortcuts as well as allowing a shortcut to be rebound (for instance, if you were to allow the user to choose a key for a shortcut).
    • Added a change event to Keyboard.manager whenever any keyboard is activated.
  • Tips:
    • NEW Tips option “windowPadding” allows you to reduce or expand the virtual size of the window for tip positioning. Defaults to {x:0, y:0}. You can use that is a workaround for the scrollbars not being considered when calculating tip positions.
  • HtmlTable:
    • fixed numerous bugs filed in Lighthouse
    • HtmlTable can no longer apply it’s click behavior more than once.
    • HtmlTable now pushes headers defined in the options.
    • Reworked HtmlTable’s DOM a bit to allow for positioning of the sort icon
    • Added new set method for headers and footers.
    • Fixed error in HtmlTable.Parsers when sorting by date. format(‘db’) was being applied to the text and not the date object.
  • Array:
    • Added Array.shuffle
  • Request.JSONP:
  • Fx.Slide:
    • Added an option to specify the wrapper element for Fx.Slide. Was already present in the docs but could not be passed as an option.
  • Mask:
    • Added options for the IframeShim for Mask

Download it with the MooTools More builder.

As usual, if you find any issues, file a ticket at lighthouse. There are already tickets open for that we are not including fixes for in this release. Look for a release for these things in the next few weeks.

MooTools 1.1 Upgrade Helper (beta)

Written By Moo Tools, on Thursday, December 31st 2009, 3:03pm

Users wishing to upgrade any large site from MooTools 1.1 to 1.2 can sometimes find it difficult. The API for 1.2 changed quite a bit, so without help upgrading your code can be fraught with danger.

Our solution is an upgrade helper that will allow you to replace your old MooTools 1.1 code with 1.2 code by logging deprecated methods to the console and telling you what needs to be changed.

The upgrade helper also attempts to automatically convert 1.1 calls to 1.2 calls. However, this helper is not really meant to be a compatibility script so much as a script designed to help you migrate your code. In almost all cases methods that have been deprecated or have had their API altered will provide feedback to the console when they are called. Ideally, developers will put this script into their environment with MooTools 1.2, use their application and change all the calls that throw warnings, then remove the upgrade helper from their environment.

Using the Upgrade Helper

You can download the upgrade helper on the MooTools Download Page along with current build of MooTools built for it. This companion library has all the functionality found in MooTools 1.1 (Drag, Accordion, etc. - some of these plugins moved out of MooTools Core and into MooTools More in 1.2).

Simply replace MooTools 1.1 with MooTools 1.2, include the upgrade helper, then include your site’s code. Browse your site with a browser that provides a console API (we recommend Firefox with Firebug) and take note of the warnings thrown (note, you can adjust the logging; see the readme). Address these in your code base until you cannot find any more, then remove the upgrade helper. You have now an upgraded website, and you can use the plugins in the Forge!

If you still have warnings after you have finished converting your code, have a look at the documentation for 1.1 and 1.2 and also the source code in the upgrade helper. Most changes are simple, but may require a change of arguments. There are a few breaking changes but in the vast majority of cases these should not affect you. A complete list of the changes between 1.1 and 1.2 can be found in the readme of the github upgrade-helper repository.

Feedback, Help, and Resources

The upgrade helper is being released as a beta for now. We’ve written and run tests against the browsers we support but the real world usage of MooTools will be the real test. As such, we hope that you, the MooTools community, will help us polish this script, by letting us know what features on your sites don’t work. Bugs can be filed using the github issues for the repository.

Arguably, this is something we should have provided long ago. Going forward, we’ve pledged to make all releases 100% backwards compatible for all documented methods and features.

Should you require any guidance or assistance, you can, as always, find us in the #mootools IRC channel or post in the MooTools Google Group.

Last of all, massive thanks to Nathan White and David Isaacson, for their early work on this. In the last few weeks the MooTools Dev team has spent a lot of time making and testing this upgrade helper, but these guys kicked this off with their contributions and they are most appreciated.

MooTools Depender - A Build Tool for MooTools JavaScript Libraries

Written By Aaron Newton, on Monday, November 9th 2009, 2:10pm

As mentioned in the new features in MooTools More in, there’s a new plugin called Depender which uses MooTools dependency mappings to allow you to lazy load additional scripts on the fly based on what you need. Rather than list every single file you depend on, you just list the features you want to use and it computes all the specific files needed and each of the files that they need (and so on), excludes the files you already have, and then injects the remaining scripts into the document, providing a callback.

Unfortunately this method is rather slow. The JavaScript plugin must inject each individual script in the dependency list and all these requests can only go as fast as your browser can make them. As a companion to this plugin, we have also authored a stand alone server side application.

New Server-Side Depender

The new server-side depender companion app ships in two forms: a PHP version and a Django version. They each have their own positives and negatives. The PHP version ships with a web-based interface — a builder you can use to check off the things you want in your download (similar to what you see on On the other hand, the Django version is faster. The Django app caches everything to memory but the PHP version caches results to disk.

Depending on your needs, you can also use these server-side applications to lazy load chunks of functionality on the fly. This obviously requires your application to talk directly to the server when it needs more code. These apps aren’t designed for enterprise scale.

The server side applications are available on github. We still consider the state of this project to be beta, but we want to get the tools into your hands now. If you have any feedback or find any bugs, we want to hear about it. Check out the documentation to see how it all works, including the Depender Client(docs), which gives you this nifty interface:

            scripts: ['DatePicker', 'Logger'], //array or single string for one item
            callback: function() {
                    //your code that needs DatePicker and Logger
    //later, you need to load more dependencies...
            scripts: 'Fx.Reveal', //array or single string for one item
            callback: function(){
                    //if, for some reason, Fx.Reveal is available already,
                    //then this function will execute immediately, otherwise it will
                    //wait for the requirements to load

Libraries that you download with Depender will all have a standard header that looks something like this:

    //MooTools, <>, My Object Oriented (JavaScript) Tools. Copyright (c) 2006-2009 Valerio Proietti, <>, MIT Style License.
    //MooTools More, <>. Copyright (c) 2006-2009 Aaron Newton <>, Valerio Proietti <> & the MooTools team <>, MIT Style License.
    //Contents: Core, Browser, Array, Function, Number, String, Hash, Event, Class, Class.Extras, Element, Element.Event, Element.Style, Element.Dimensions, Selectors, DomReady, JSON, Cookie, Swiff, Fx, Fx.CSS, Fx.Tween, Fx.Morph, Fx.Transitions, Request, Request.HTML, Request.JSON, More, Element.Shortcuts, Element.Measure, Fx.Reveal
    //This lib:

This header includes, among other things, a manifest of the contents of the file and a url that can be used to retrieve it again. This is especially useful if you want to come and download the file again for the latest version.

The builder on does not use Depender yet but we will deploy it there soon. You can see it live on the Clientcide builder.