We recommend that all users upgrade to 1.4.4 as soon as possible.

Fixes

• #2160: Fx.Tween/Fx.Morph problem with ‘%’ unit
• #2175: IE Leak: Array.flatten
• #2178: IE doesn’t set value when creating element if css attributes are used
• #2241: Slick.finder index selector
• #2247: Element.get not reading custom attributes in IE7/8
• #2248: contains causes “Out of Stack Space” in IE
• #2252: Element.getParents doc clarification
• #2262: SVGAnimatedString causes Slick error
• #2266: Calling setOpacity with null does not remove the style
• #2275: Update Slick to 1.1.7

Known Issues

• #2184: IE9 on Windows Server throws exception; can’t continue
• #2194: Function#bind ES5 bug when bound function is called as part of a new expression
• #2199: Browser.version always returns the same for Android 2-4
• #2207: Fx.cancel() should clear animation so Fx.resume() will not continue it
• #2214: IE8 - Cannot inject into window.opener
• #2225: IE in-page memory leak when using removeChild
• #2236: IE8 tween/morph clip:rect breaks
• #2243: Memory leak with request class
• #2245: Element.getOffsets() is broken in iOS 4.3 if using -webkit-transform
• #2265: new Element(‘style’, {text: ”}) throws IE exception
• … and more

These issues will be fixed subsequently prior to release of the next maintenance release, 1.4.5.

Contribute

These fixes and improvements would not have happened if you didn’t submit an issue (ticket) to the MooTools Core Issues, or reporting your problems in the MooTools User Group. Send us your (MooTools) issues (or feature requests) so that your favorite JavaScript framework keeps getting better.

Get it!

• Download MooTools Core 1.4.4; Build MooTools Core 1.4.4
• Fork / clone MooTools Core 1.4.4 from GitHub, and build it yourself with Packager.
• Google CDN (will be updated soon)
• Browse the Documentation for Core & More.

Fixes

• #2109: IE7/8 getProperty returns functions
• #2110: Documentation: Request.JSON’s behaviour of onFailure
• #2117: Document conflicts between Array and Elements methods
• #2121: Missing Fx.options.frameSkip documentation.
• #2126: Re-add undocumented from argument to Element.fade
• #2127: Element.js memory leaks
• #2146: Add Element.NativeEvents to docs
• #2150: Add Fx.isPaused() method
• #2152: Packaging issue. Build header and Core.js yml header collide
• #2155: Add special note to Element.empty
• #2163: IE7 Crash with Mootools Core 1.4.2
• #2164: Cannot set numerical 0 values to form fields.
• #2169: Array#filter should store this[i] in a variable before calling the callback.
• #2170: propertychange on an input[type=radio] with this.checked fires standard onChange
• #2176: uid remnant which prevented proper cleaning of elements and their storage
• #2182: element.erase( ‘html’ ) sets content to text ‘undefined’

Known Issues

• #2129: < IE9 sets width/height attribute once, and doesn’t update on other loads
• #2130: Object.each doesn’t address IE DontEnum bugs like Object.extend and others
• #2160: Fx.Tween/Fx.Morph problem with ‘%’ unit
• #2168: Fixes 2129.
• #2175: IE Leak: Array.flatten
• #2178: IE doesn’t set value when creating element if css attributes are used
• #2183: Incorrect event.key from some keypress events in Firefox
• #2184: IE9 on Windows Server throws exception; can’t continue
• #2185: Fix #2184: IE9 on Windows Server throws exception; can’t continue
• #2188: Fixes #2178 - A input field should keep its value even when the type property is changed (in IE)
• #2189: Uncaught TypeError: Property ‘id’ of object # is not a function
• #2193: Element clone storage again
• #2194: Function#bind ES5 bug when bound function is called as part of a new expression
• #2196: it’s better for getStyle method always returns style value with px unit
• #2199: Browser.version always returns the same for Android 2-4
• … and more

These issues will be fixed subsequently prior to release of the next maintenance release, 1.4.4.

Contribute

These fixes and improvements would not have happened if you didn’t submit an issue (ticket) to the MooTools Core Issues, or reporting your problems in the MooTools User Group. Send us your (MooTools) issues (or feature requests) so that your favorite JavaScript framework keeps getting better.

Get it!

• Download MooTools Core 1.4.3; Build MooTools Core 1.4.3
• Fork / clone MooTools Core 1.4.3 from GitHub, and build it yourself with Packager.
• Google CDN (will be updated soon)
• Browse the Documentation for Core & More.

Changes

• Lots (and by that I mean LOTS) of documentation improvements, clarifications and cleanups
• Updated Slick to 1.1.5 and improved the speed of our Slick selector engine
• Added delegation support for submit, focus, blur, reset, change and select events in MooTools More
• If available the native JSON methods are now used in JSON.decode and JSON.encode
• Multiple Pseudos click:relay(a):once (demo)
• Two new pseudo events: :throttle and :pause
• Added String.truncate to String.Extras in More
• More than two hundred changes to increase the stability of both Core & More

I am also pleased to announce our newest addition to the MooTools More team, Jacob Thornton, who is a great developer, currently working for Twitter. He has put a substantial amount of work into making MooTools More even better.

Be sure to check out the updated demos in our new demos section.

Get it!

• Download MooTools Core 1.3.1; Build MooTools Core 1.3.1
• Build MooTools More 1.3.1.1
• Fork / clone MooTools 1.3.1 from GitHub, and build it yourself with Packager.
• Read the commit logs to see precisely what has changed.
• Browse the Documentation for Core & More.
• Please report any bugs you can find on Lighthouse, our bug tracker.

Awesome new features? What awesome new features?

Events.Pseudos, wait, this isn’t happening!

MooTools Core 1.3 includes our new selector engine Slick. One of Slick’s components is Slick.Parser. Slick.Parser parses a CSS selector to an object representation of the selector, called a “Slick object”. Since our Event Delegation already uses such a CSS style notation for defining events, i.e. click:relay, we decided to take this to the next level: Events.Pseudos and Element.Event.Pseudos. I’ll show you an example of how it works:

document.addEvent('keydown:keys(shift+c)', function(){
    alert('You pressed the shift and c keys!');
});

We append an event pseudo, :keys to the existing event name, to get custom events. This doesn’t only work for Element events, but for the Class event system, the Events mixin, as well. Currently we’ve implemented the pseudo events :once for both Events as Element.Event and :keys and :relay for Element.Event.

Locale, localizzazione, Lokalisierung, localización, локализация

For 1.3 we’ve rewritten MooTools.lang to Locale. It’s now more powerful and has a much better API. A big thanks to our community as well! A lot of people helped us improve translations for their native languages.

A simple example looks like:

Locale.use('nl-NL');
Locale.get('Ping.stop'); // w00fz, kun je alsjeblieft stoppen met pingen

However, the real cpower of the new Locale is its inheritance abilities. For example, if you take Portuguese, it’s used in several countries around the world, like in Brazil. Brazilian Portuguese is slightly different, but has many similarities. Now instead of recreating a whole Locale Set file, you can now inherit the Portuguese translations and overwrite only the values that are different.

Locale.define('pt-BR', 'ping', {
    // ... key-value pairs
}).inherit('pt-PT');

Another awesome thing is the new Locale.Set.From function which right now allows you to create Locale Sets from a JSON string. The plan is to extend this in the future to support other data formats. This function will make it easier to share translations between server and client side: you can do a Request to your server, and pass the responseText to Locale.Set.From right away.

Number.format

Because Localization is more than just converting strings to other languages, we added Number.Format to MooTools More. Just like our Date.format works for dates, Number.format lets you format numbers in various formats.

(101).formatCurrency(); // € 101,00

HtmlTable

HtmlTable has received a lot of attention. Its API is a little more useful now, but there are numerous features added including the ability to select multiple rows with shift and ctrl, keyboard support, and more robust sortability controls.

Notable changes in 1.3

• A total of 105 tickets closed for 1.3.0.1 (first 65 tickets here, 28 tickets here, and another 12 here)
• Hash has been deprecated in 1.3 Core. But fear not! More 1.3 provides Hash now.
• Hash.Extras are now also available as Object.Extras
• Event Delegation now supports the mouseenter and mouseleave events
• Log.js has been removed. Use this or this or just console.log and friends.
• Like myElement.get(‘tween’, options) Fx Classes in More don’t support the second argument of Element.get anymore either. You can find more information in the Update Wiki Page
• EcmaScript 5 array methods Array:reduce and Array:reduceRight are added to Array.Extras
• Date.parse now follows the UNIX specification of strftime.
• Full changelog for 1.3 (Note that changes that we also applied for 1.2.5.1 will be listed under 1.2.5.1)

Testing

Like Core and Slick we have moved More to use our new Specs Runner. We tried to cover as much as possible in the Specs. However, More contains a lot of UI components that are very difficult to test with the Specs. Therefore we have new UI tests, which are basically HTML pages with JavaScript and CSS. You can run the tests with mootools-test-runner (Python + Django) or mootools-ui-runner (PHP)

MooTools 1.2.5.1

Together with this 1.3 release we also release MooTools More 1.2.5.1, which is an update for the 1.2 branch for the people who are not (yet) able to upgrade to 1.3. It has the improved stability of 1.3 and some new features.

Notable changes in 1.2.5.1

• There are 65 tickets closed since the previous 1.2.4.4. release.
• All optimizations and updates done to existing code in 1.3.0.1 are applied on the 1.2.5.1 branch as well
• Depender.js is no more, use Packager or Depender on the server side.
• Full changelog for 1.2.5.1

Get It NAOW, with a smile!

• MooTools More 1.3
• MooTools More 1.2.5.1
• Fork / clone MooTools More from github
• See changelog
• Browse the Documentation 1.3 and 1.2
• Please report any bugs you can find on Lighthouse, our bug tracker.

MooTools Core 1.3 brings the following new and improved features:

Core

We have revised the whole base of our Core framework to speed up MooTools, provide an even more beautiful API and to make it future-proof. In order to reduce the number of global variables, we have moved all $-prefixed functions into the most appropriate namespaces available ($splat → Array.from, etc…). In short, with 1.3 you are getting the best MooTools experience ever.

Slick

MooTools Core 1.3 includes Slick, our new standalone selector engine. Slick is a new official MooTools project developed by Thomas Aylott, Fabio Costa and Valerio Proietti with help from a vast assortment of JavaScript heroes, villains, trolls and kings.

Even if you can’t use MooTools Core in a project, you can still use Slick! It’s standalone, so instead of Slick requiring anything in MooTools, Core now heavily relies on everything that is Slick.

Slick supports almost every selector you could ever think of and paves new ground with tons of new selectors that you may never have thought possible. The engine is incredibly customizable and supports ninja magic such as reverse combinators.

Slick is unparalleled in its accuracy! We created an implementation agnostic test suite called the SlickSpec. It includes over 3,000 tests that cover the gamut from the wildest unicode edge case to insanely complex interactions when switching between multiple contexts and documents in more doctypes than you could stick.shake() at. Not to mention the obligatory bizarre browser-specific bug fixes and workarounds. We haven’t kept all this goodness to ourselves, we’ve worked hard to implement this test suite in a way that all other selector engines can use it.

Stay tuned in the coming days and weeks. We will certainly be posting much more about Slick and release a dedicated website for it.

Some Examples:

All div elements and p with the class ‘moo’

myElement.getElements('div, p.moo');

All direct child div elements with the class ‘cow’

myElement.getElements('> div.cow');

Search for the first parent that matches ‘div.cow’, matches the next ‘div’ sibling and returns the first input element that it contains. Ain’t that awesome?

myElement.getElement('! div.cow ~ div input');

1. Using the barF iframe document as the starting point context
2. Find me the first div
3. whose direct parent is a blockquote
4. whose next sibling is a ul
5. who contains an element with the id foo.

Slick.find(barF, '#foo ! ul !~ blockquote > div');

Interactive example

Element

With the addition of Slick and its new standalone CSS selector parser, we gained the ability to create elements using a CSS expression. I promise that you will love this feature!

new Element('div#cow.moo.big[data-size=5]');

Other Stuff in Core 1.3

• Revised Core.js, added even more abstractions
• Fixes for a lot of element attributes (maxlength, etc…)
• New feature tests further minimize reliance on browser detection
• New Browser.js for the rare times when feature detection doesn’t cut it
• New DOMReady implementation improves speed and fixes edge case bugs
• Array.each now chains! Yes, indeed.
• Support for touch events on breakthrough communication devices
• Array: forEach, map, some, every and filter now behave according to the ES5 Spec in IE (skipping undefined values)
• IE opacity style fixes
• If you build without 1.2 compatibility, Hash is gone. MooTools More 1.3 will provide Hash from now on.
• Elements is now an array-like-object instead of a real array.
• Additions to Request — authentication, onprogress and other cool stuff
• Numerous stability improvements
• … and more!

Roll your own with Packager

With MooTools Core 1.2.5 and Core 1.3 we have introduced new headers in all of our JavaScript files that allow you to build your own custom edition of MooTools from the command line. Every file can now “provide” and “require” certain functionality. For example, Class.js provides “Class” and requires “Array, String, Function, Number”. Dependencies can even be specified cross-package; one GitHub repository equals a package and thus can be registered to Packager. You can find more information about Packager and a detailed README on kamicane/packager on GitHub.

All you need to do is clone the GitHub repositories that you need, register them with Packager and build. Packager will calculate all the dependencies from the source files in your registered packages and hand you a freshly baked copy of MooTools with all the goodness you need and nothing you don’t. You get all that magical goodness for free, invented by our amazing Valerio Proietti and honed to perfection by the MooTools Developers. You can find a lot of packager ready plugins for MooTools Core 1.3 on @kamicane’s GitHub or @cpojer’s GitHub (It’s-a-me!).

If you prefer Python, fear not! There is also an implementation using Django called Depender which allows you to do on-the-fly-building and compressing of your files.

Function.prototype.bind and Element.get with multiple arguments

We’ve had our own implementation of Function.prototype.bind in MooTools Core long before the ECMAScript 5 Standard was a twinkle in Douglas Crockford’s eye. Given that we fully support ES5, we have changed our implementation to match this new standard. However, you will only get the new implementation if you drop the 1.2-compatibility-layer.

Element.get used to be able to work both as a setter and getter. As described a few months ago when we announced 1.3 beta2, we are now changing this behavior to ensure a consistent API.

The issues that may arise with these two changes are described in the Update Guide from 1.2 to 1.3. If you experience any problems while updating or upgrading, feel free to jump in on IRC (#mootools on irc.freenode.net) or post on the Mailing List so we can help you get your websites and apps running!
Don’t forget that you can use jsFiddle.net to help the community answer your specific questions.

Testing

Thomas has always encouraged (and by that I mean forced) everyone to do test-driven-development. The only problem was that our old spec engine took forever to run in fast browsers. In slow browsers you were able to drink a coffee while watching the specs run. A few months ago, Arian and I rewrote our current engine which is now used by all major MooTools projects. It is still a work-in-progress and you will hear more about testing in later blog posts. The good news is that with MooTools Core 1.3 we have specifications that cover 95 % of the code base and all of our code is tested when you run the specs, which now takes less than two seconds.

MooTools More 1.3RC

After literally hundreds of bug fixes, plenty of new features and even a few new team members, we feel that it is the right time to provide a release-candidate of MooTools More 1.3 so that you can instantly get started with 1.3. You will find more information about MooTools More and all its new goodies very soon (once it loses the RC tag).

Get it while it’s hot!

• Download MooTools Core 1.3; Build MooTools Core 1.3
• Build MooTools More 1.3RC
• Update from 1.2 to 1.3 with 1.2 compatibility.
• Upgrade from 1.2 to 1.3 and drop 1.2 compatibility.
• Fork / clone MooTools 1.3 from GitHub, and build it yourself with Packager.
• Read the commit logs to see precisely what has changed.
• Browse the Documentation for Core & More.
• Please report any bugs you can find on Lighthouse, our bug tracker.

• 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!

This is mostly a bug fix release.

• Nearly 50 bug fixes (see the milestone for 1.2.4.3 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:
  • Made JSONP pass all arguments, not just the first, to its complete/success methods; see this discussion on the google group.
• 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 1.2.4.4 that we are not including fixes for in this release. Look for a release for these things in the next few weeks.

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.

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 MooTools.net). 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:

    Depender.require({
            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...
    Depender.require({
            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
                    $('someElement').reveal();
            }
    });

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

    //MooTools, <http://mootools.net>, My Object Oriented (JavaScript) Tools. Copyright (c) 2006-2009 Valerio Proietti, <http://mad4milk.net>, MIT Style License.
    //MooTools More, <http://mootools.net/more>. Copyright (c) 2006-2009 Aaron Newton <http://clientcide.com/>, Valerio Proietti <http://mad4milk.net> & the MooTools team <http://mootools.net/developers>, 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: http://clientcide.com/js/build.php?requireLibs=mootools-core&require=Fx.Reveal&compression=none

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 MooTools.net does not use Depender yet but we will deploy it there soon. You can see it live on the Clientcide builder.

The value in making this change is allowing developers to use more than one framework within a page (which is NOT something we recommend or endorse, but we recognize this is not always under the developer’s control). Not relying on the dollar function prevents the need for jQuery.noConflict() when using jQuery and MooTools together, for example. If no other framework is detected, however, $ will be assigned to MooTools. This means that all of your current MooTools code WILL NOT break. It does, however, mean that if you want to use MooTools and jQuery together (without using jQuery’s noConflict mode), instead of using $ in your MooTools code, you’ll have to use document.id().

If you want your MooTools plugins to be cross-framework compatible, you’ll have to replace all the instances of $ with document.id().This change only applies if you’re using more than one framework on your pages. If all you use is MooTools, nothing will change for you. Look forward to more details about Framework compatibility mode in a future post.

MooTools Core & More Updates

While we encourage you to browse LightHouse and the histories for MooTools Core and MooTools More to get the most detailed list of changes, the following significant updates were committed in MooTools 1.2.3:

Core

• Element: MooTools compatibility mode: the $ function is only defined if no pre-existing $ function is found. If an existing $ function is found, you can use document.id()
• Element: changed internal instances of $ to document.id
• Core: fix for server-side MS JScript 5.x; makes MooTools more friendly for server side programming
• Class: Class doesn’t require Browser, removed from scripts.json
• Element: Fixes for set/get Property
• Element.Dimensions: fix for webkit body.scrollTop inconsistency, getBoundingClientRect used whenever possible (not just for Trident), renaming element.position to element.setPosition; adding docs for the method; alias is included in-line for compatibility
• Hash: Hash extend no longer uses the window if no arguments supplied
• Request: clearing Request readystate before calling success or failure;
• Selectors: Added :enabled pseudoselector, was in the Docs but not implemented.
• Docs: Fixed docs headers for first-child, last-child, and only-child.
• Internal: UnitTester test suite is now a git submodule
• Numerous small fixes, speed improvements, documentation tweaks, etc.

More

• Per the change in -core, $ is no longer used (uses document.id instead)
• Element.Measure: trying cssText solution for Element.expose (again).
• Element.Forms: swapping feature detection for browser support per
• Date: Massive refactoring of Date.js and Date.Extras.js
• Drag.Move: Fixing drag with grid issues
• IframeShim: altering zindex assignment in IframeShim to better ensure that it’s always underneath the shimmed element, updating Iframeshim’s empty document creation; fixes https issues in IE6
• FormValidator: reworking formvalidator scroll-to logic to be a little more efficient
• OverText: preventing overtext from focusing on inputs except when they are interacted with (so OverText.update() does not focus an input);now stops polling when elements are hidden (when polling is enabled)
• Fx.Scroll: adding scrollIntoView method - scrolls an element so that it is completely visible; if below the view, scrolls down until it is at the bottom of the screen, if above, scrolls up until it is at the top.
• JSONP: was calling (the deprecated) this.request instead of this.send during retries
• URI: Adding set(‘data’, obj) to set
• Assets: adding error callback for Assets.images
• Tips: removing dependency for Element.Measure for Tips; updating CSS class name in OverText
• Numerous small fixes, speed improvements, documentation tweaks, etc.

MooTools 2.0 is on the Horizon

As mentioned above, 1.2.3 is likely the last update for MooTools 1.2. MooTools 2.0 will introduce numerous performance improvements and new features. We want to stress that MooTools 2.0 will feature 100% compatibility with MooTools 1.2.x.

Thank You!

Thank you for the bug fixes, feature requests, and support during MooTools’ 1.* lifetime. You, the MooTools community, have helped make this framework better with every bug found and question asked on the forum. We look forward to releasing MooTools 2.0 this summer and getting feedback from everyone in this awesome community.

• Removed debug statement that enabled IframeShim in all browsers by default
• Fixed a few docs typos
• Removed UTF-8 charset signature on String.QueryString and URI.Relative
• Assets.image now have an onError option and handle image load failure more gracefully
• FormValidator.Inline had issues displaying some of it’s validators when input values changed
• OverText now allows you to specify the element type for the label test (defaults to “label”)
• Fixed an issue with addRequests in Request.Queue; the arguments were reversed (addQueue still worked fine though)

None of these changes should affect your usage of the class, except, possibly, the change to OverText, as the element it previously created for the labels was a div. If you styled these with css and referenced the tag name, you’ll either need to update your css reference or pass in element: “div” as an option when you invoke the class.

Core

MooTools 1.2.2 is a mainly a bug fix release but it also includes an almost entirely new Class.js. The reasoning behind this is that the old Class.js didn’t play nicely with some advanced usages of this.parent() present in the new MooTools-More. We already had the script ready and tested in the MooTools 2.0 branch so we simply “backported” it to 1.2.2. Other than providing the parent fixes, the new Class also features a much more robust inheritance model, especially when dealing with objects.

For example, the objects you implement now in a class are merged if an object with the same name is found in the class prototype:

var Animal = new Class({
    options: {
        color: 'brown',
        says: 'hissss'
    }
});

Animal.implement('options', {says: 'meow'});

// Animal.prototype.options is now {says: 'meow', color: 'brown'};

This is especially useful when overriding default options in classes, such as Request.

Another object-oriented feature we introduced is that now sub-objects are actually inherited Parent-to-Child. If you implement a new option in Animal, then Cat, which is a subclass of Animal, will get the new option as well, and so will every instance already existing. An example:

var Cat = new Class({
    Extends: Animal
});

var kitty = new Cat();

Animal.implement('options', {nu: 'one'});

Cat.prototype.options.nu == 'one' //true
kitty.options.nu == 'one' //true

This obviously also applies to methods.

Additional changes to the MooTools Core in 1.2.2 are mostly minor bug fixes.

More

One of the new features of MooTools-More, since the last RC, is that it is now possible access the previous state of overwritten methods of classes through Class.refractor. An example:

var Cat = new Class({
    energy: 0,
        eat: function(){
            this.energy++;
    }
});

Cat = Class.refactor(Cat, {
    eat: function(){
        this.previous(); //energy++!
        alert("this cat has " + this.energy + " energy");
    }
});

This functionality allows users to integrate seamlessly with existing classes, and add to existing methods without the need to subclass.

We’re considering some way to make this behavior more generic for a possible inclusion in MooTools-Core 2.0.

The first RC of MooTools-More produced a lot of feedback and contributions that we’ve integrated as we prepared for our full release. Following this full release of the new MooTools More plugins, we’ll begin adding new features quickly and regularly with what we hope will be biweekly releases.

Today, I have an answer. The only way to give you a better MooTools is to give you more of it. It’s that awesome. Today, we’re making MooTools awesomer.

We give you the new and improved MooTools More - the official plugin collection for MooTools. The plugins we are releasing today take the fifteen files previously in MooTools More and triple them. That’s three times the awesome!

What’s in it you ask? Well, let me tell you. The new and improved -more currently includes:

• Class extensions including a Binds mutator, easier refactoring, chain pausing and more.
• New Native extensions including more love for String and Array, plus a fully featured Date Native and a URI extension to make managing links downright fun.
• More Element love with help for managing text selection and relative positioning (put this box’s lower right corner next to the upper right corner of that other box…)
• Form love including a robust and extensible form validator and a class for displaying hint text over an input.
• Extended Request functionality including JSONP support and Queuing.
• Support for language localization for classes that output text (days of the month, months of the year, form validation errors, etc)

Oh, and we’ve already translated the text content in these new plugins (Date and FormValidator specifically) into half a dozen languages thanks to all the helpful folks in the MooTools-Lang user group (do you know a language other than English? Want to help? Here ya go).

I know, you can barely contain your excitement. Us too! Surely, you ask, there must be a catch to all this awesomeness. Does it cost four easy installments of $19.99? Shipping and handling? Must you sign an oath? Nay! It’s free for the taking.

But there are a Few Catches

First, today’s release is just the beta - the first release candidate (RC1). This means that you will certainly encounter problems, which would imply that it’s not 100% awesome (you are wrong! It is 100% awesome - when the beta is finished and we officially release it it will be 125% awesome).

But yes, you may encounter bugs. In this case, you will need to file it in the shiny new MooTools-More dedicated Lighthouse. Industrious types are encouraged to pull the repository from github and try and fix things themselves - helping hands are always appreciated.

In addition to this, the docs for the beta are in a different location (links at the bottom). The search in these docs still points to the google search for the current docs, so the new stuff won’t be returned if you use the search.

Also note that there is not a compatibility layer yet written for this release. There are only a handful of items from the previous files that were in MooTools More. For those of you using the Clientcide libraries, you’ll see a lot of familiar scripts on the list, and there are numerous changes between the versions on Clientcide and the versions here. You can see the list of breaking changes in the readme.

Enough! Give It To Me!!!

Ok, ok, you want links? Here you are:

• The Docs for MooTools More RC1
• Download MooTools More RC1

How You Can Help

There are several things you can do to pitch in. First, you can run the tests in all the browsers you have access to. There are two types of tests:

• The Specs Tests
• The User Tests

Running through these in your browsers and reporting anything that seems wonky will help us tremendously. If you know a language that hasn’t yet had the translation written for Date or FormValidator, you can, as mentioned previously, jump into the MooTools-Lang group and help out with that.

More to Come

MooTools More is now it’s own official project which means its release schedule is no longer tied to MooTools Core. Once this release candidate is fully released (hopefully in the next week or so) expect to see new plugins arrive every week or two. Our objective is to quickly grow the plugins available here as well as address bugs in MooTools More constantly. We have a long list of functionality already lined up for future releases. This is only the beginning! If you want to get involved, read more on the MooTools More wiki.

Thanks

Special thanks go to the MooTools More team zilenCe (Christoph Pojer), devthought (Guillermo Rauch), David Walsh (er, David Walsh), and the numerous others who helped in the development of this release. Seriously, there were a lot of people who chipped in. You can too, if you like.

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…

Links:

• Changelog
• MooTools 1.2.1 Download
• MooTools 1.2.1 Builder

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 the last version of MooTools to support Safari 2 and Opera 9.5. These browsers have been advancing at a tremendous pace, and have a user base which updates regularly, so we don’t think this will be much of an issue when the time comes. Note that you don’t need to worry about this for quite some time yet because 1.3 is a long way off, but we just thought this was a good place to let everyone know.

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.

Where Have the 1.11 Docs and Demos Gone?

The 1.11 docs have been moved to http://docs111.mootools.net. Conversely, the 1.2 docs have been moved from http://docs12b.mootools.net to the main docs subdomain (http://docs.mootools.net). The same is true for demos.

• 1.11 Documentation
• 1.11 Demos
• 1.2 Documentation
• 1.2 Demos

1.2 is Totally New

Don’t let the version number fool you. 1.2 is not merely a minor revision of 1.11. As those of you who have been reading the blog will be aware, 1.2 has a completely updated API and is not compatible with 1.11 code. You can, however, utilize the compatibility layer that has been built to make the transition to 1.2 easier.

• Core Compatibility File
• Plugin Compatibility File

Since most of the changes between 1.2 and 1.11 have been documented in earlier posts to this blog, I won’t go into the details here.

Offsite Hosting of Version Management, Tickets, and Discussions

Because of the increasing popularity of this project of ours, we have been under an increasing amount of stress to keep the various parts of this site running in good order. You may have experienced downtime relative to MooTools recently. We understand that many developers utilize MooTools in critical components of their projects, and such downtime is completely unacceptable.

To solve these issues for the 1.2 release, we have moved our critical components offsite to the best provider of each component, granting MooTools users with the highest possible uptime of all areas of the site. A major benefit of this move is being able to completely reinvent the way we interact with our community of users (aka you guys!).

Git

Along with the 1.2 release comes our shift from Subversion to Git. Git is a huge step forward to our development model, allowing everyone who wants to contribute to MooTools the ability to create their very own fork. Each fork can then be merged into the main core as seen fit or used on its own as an alternate version of MooTools. This allows us to release faster, iterate to better versions and better handle the contributions of the community.

This allows would-be contributors to play in their own sandbox without worrying about whether or not their suggestions are appropriate. So get forking!

Please note that the Subversion repository will no longer keep up with changes to MooTools. You will have to check out the Git repository for that.

To keep the core lean and mean, we have created a separate repository for plugins, called “More”. Plugins are defined as specialty components which aren’t crucial to the core functionality of MooTools. This includes modules which have been part of the core distribution until now.

You’ll also notice that the download page has been split into two pages, one for Core and one for More. (Further repositories may be coming in the future if we can think of more rhyming names.)

GitHub

We’re using GitHub to host our new Git repositories. We now have one respository for Core and another for More. The folks over there have given us an extremely warm reception, and we are likewise very happy to have such a great service at our disposal.

Bug Tracking by Lighthouse

We have abandoned our Trac, which has been giving us problems over the past weeks, for Lighthouse. Lighthouse allows us to integrate our ticketing system with our new Github account and should provide everyone with a comparable experience to our previous system.

You can visit the new Lighthouse account here.

New MooTools User Group

As part of our offsite initiative, we have moved the community forum to Google, where it hopefully will not crash and die. The forums will be back shortly, but only as a read-only archive.

Join Us on IRC

While we’ve been partying in the IRC room for quite some time, the IRC link to #mootools on Freenode has been added to the main page of MooTools.net. If you have not visited us there before, please feel free to stop by to ask your questions or just hang out. We love chatting with new users.

New Faces

One last note is that we’ve added two new members to the MooTools production team, Jan Kassens and Thomas Aylott. Both of them have been working extremely hard for quite some time now to bring you a better framework, and we’re very happy to give them formal recognition.

Links In Case You Missed Them

Docs and Demos

• 1.11 Documentation
• 1.11 Demos
• 1.2 Documentation
• 1.2 Demos

Compatibility

• Core Compatibility File
• Plugin Compatibility File

Git Repositories

• Core Repository

• Plugin Repository

  THE SUBVERSION REPOSITORY WILL NO LONGER BE UPDATED.

Bug Tracking / Tickets

• MooTools at Lighthouse

Community Discussion

• MooTools Users at Google Groups
• #mootools on Freenode