The first beta for MooTools 1.2 is finally here!After months in the making, we can confidently say that MooTools 1.2 is now feature complete. However, there are still some bugs left to squash.Head over to MooTools download page to start playing with it right away.A Note About CompatibilitySome parts of MooTools 1.2 aren't immediately compatible with those found in MooTools 1.1. In the downloads page, you'll find a box that says: "include compatibility with previous version". Clicking that box will add the missing pieces and will make MooTools 1.2 play nice with code written for MooTools 1.1.New stuff that we already covered:The amazing HashSpecs!Effects EnhancementsImportant stuff thats ...

MooTools has always been known for having some of the most fluid and impressive effects around. In 1.2 we've introduced some exciting new enhancements that make them even more efficient, powerful, flexible, and easy to use. Here are the changes made to the Fx Classes to take note of...What's in a name?One of the most obvious changes to the MooTools Fx Library is a change in the naming of Fx.Style and Fx.Styles. Though you can still use these class names in 1.2, they will be deprecated in future versions, so please start using the classes through their new names, Fx.Tween and Fx.Morph respectively. The reason for the name change is two-fold. First, we feel these names more explicitly ...

Here's what you guys have been dying for: a presentation talking about MooTools. Presented by yours and only: ibolmo! The presentation tries to cover all the major aspects of MooTools to solve the familiar question: "What's different about MooTools?" I talk about jQuery and Prototype and how they differentiate themselves from MooTools. Lastly, there's a whole slew of demos and showcasing.<object type="application/x-shockwave-flash" height="300" data="http://www.vimeo.com/moogaloop.swf?clip_id=418874&server=www.vimeo.com&fullscreen=1&show_title=0&show_byline=0&show_portrait=0&color=01AAEA" width="400"> <param name="quality" value="best" /> <param name="a...

It’s been three months to the day since the last point release of MooTools and we’re excited about all the goodness packed into this release. At this point, the 1.2 codebase has a very stable API, and our current plan is to release these point releases every three months or so until the 2.0 codebase is online. If we find any serious bugs, though, we’ll be sure to get fixes into your hands as fast as we can.Non-breaking ChangesBefore we get started telling you all the yummy stuff we’ve got for you, let us first assure you that the code we released today is 100% backwards compatible with the previous versions. Upgrading should be as simple as dropping the new files i...

We haven't had this blog for very long, and talking to many users recently, I became aware of the fact that many people just don't understand how powerful MooTools actually is. The purpose of this series of articles is to shed a little light on some of the functionality provided by MooTools that many users might be missing. I think maybe it's time we got everyone caught up to speed. First topic... Natives and Elements!A quick note about this articleSo I know I said my next article would be about the new Element shortcuts added in 1.2, but there are so many other things we should probably talk about first! All the code examples featured in this article are intended for MooTools 1.2. A...

There’s always a lot going on behind the scenes with the MooTools javascript framework. And how could there not be? Here’s a look at what’s coming in the next few months.MooTools Core 1.2.4 and 1.1.2As we turn our attentions towards MooTools 2.0, version 1.2 will not receive any significant upgrades. However, until MooTools 2.0 is released we will continue to support the current version with bug fixes. To that end we’re releasing MooTools Core 1.2.4 which fixes several small bugs and addresses a change coming in the next release of Firefox. Because of this inconvenient Firefox change, we’ll also be releasing MooTools Core 1.1.2, an update to the 1.1.1 relea...

Today we give you what will likely be the final release of the MooTools Core before the jump to 2.0. While MooTools 1.2.3 is primarily a bug-fixing release, MooTools 1.2.3 also introduces an important new feature: Framework compatibility mode.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...

You’ve probably noticed a flurry of MooTools 1.2 updates recently, including updates to both MooTools Core and More. We’re happy to give them to you and hope you continue to upgrade your existing MooTools 1.2.x builds. We would like to bring to you attention an upgrade to the MooTools 1.1.2 build and MooTools 1.2.4 build which should be considered a mandatory upgrade for developers still using MooTools 1.1 and MooTools < 1.2.4.Firefox 3.6 and document.getBoxObjectForThe reason we stress the upgrade to MooTools 1.2.4 and MooTools 1.1.2 is the removal of the document.getBoxObjectFor method in the upcoming Mozilla Firefox 3.6 release. Within the browser detection code of MooT...

As mentioned in the new features in MooTools More in 1.2.4.1, 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...

There’s nothing like releasing code to uncover glitches. Since last week’s release of MooTools Core 1.2.4 and MooTools More 1.2.4.1, there have been a few bugs reported and we wanted to get the fixes out to you as quickly as possible. Most of these are minor. We have unit tests for all the classes we release, but writing a test for every possible configuration is tough, and it’s the real world that sees these features used in ways we can’t imagine.Today’s release offers no new features, a lot of very minor fixes (to docs and the like), and the restoration of a few changes to the API that weren’t intended (Tips and Fx.Slide, in particular).Here’s w...

Today we're going to talk about Swiff, which lets you combine Flash and JavaScript to do things MooTools can't do on its own.What's Swiff?Though an earlier version of Swiff has been packaged with Harald's FancyUpload, it's officially new the MooTools 1.2 distribution. Swiff allows for communication between Flash movie (.swf) files and the page's JavaScript, opening up possibilities not available with JavaScript alone.The Best of Both WorldsUnless you're a diehard fan of the embedded Quicktime movie, you might see the benefit in a Flash video player to provide smooth playback of videos to your users, while still yearning for full control over the action using JavaScript and MooTools.It's ...

Today we’re releasing a small update to MooTools More that address a few bugs and minor feature requests that cropped up after the initial launch. Briefly, these are the things changed since 1.2.2.1: 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 is...

Over on Clientcide we’ve got a post up asking for feedback about changes planned for MooTools 1.3. Most of the changes are things you won’t notice - things under the hood as well as bug fixes and the like. But there are some changes under consideration that would effect existig code. We’d love to hear your feedback as we consider these changes.

Today we released MooTools version 1.11.In this release we fixed a bunch of memory leaks issues, as well as some minor bugs around.Other than some maintenance, we added the getText and setText Element methods, to help filling HTML Elements, Style tags and Script tags with text, and we added more details to the documentation.This is a recommended update for all of you using MooTools 1.1.If you want to, you can see the changelog in details.So, go ahead and give it a try!

Today I found a nice article on coderseye.com: I spent a half hour tinkering around in Aptana, downloading MooTools 1.1, and setting up a few tests. The result is extremely pleasing. Not only is MooTools way better and easier to use than I remember, but it works out of the box with AIR.That's Very nice to know!I personally haven't yet tried MooTools in AIR extensively (i only did a few basic tests) but I'm definitely looking forward to creating something in the very near future. Maybe a downloader app? We'll see!