This Moo’s For You! MooTools 1.2 Has Arrived!

By  on  

U2's been singing this week because Monday was a beautiful day. Monday marked the release of MooTools 1.2, a landmark release. CNET's Aaron Newton (and MooTools developer) was so blown away by Valerio and Co's new ideas that he wanted to name this release 2.0 but Valerio chose to keep this version as 1.2. If you'd like details on the new improvements, please visit the MooTools blog.

Even though Moo 1.2 was just officially released, I've been delivering no-bull MooTools 1.2 articles for months now. Download the newest Moo and check out my articles:

 

Recent Features

Incredible Demos

  • By
    Introducing MooTools ScrollSide

    This post is a proof of concept post -- the functionality is yet to be perfected. Picture this: you've found yourself on a website that uses horizontal scrolling instead of vertical scrolling. It's an artistic site so you accept that the site scrolls left to right.

  • By
    Submit Button Enabling

    "Enabling" you ask? Yes. We all know how to disable the submit upon form submission and the reasons for doing so, but what about re-enabling the submit button after an allotted amount of time. After all, what if the user presses the "stop"...

Discussion

  1. Well, since I’ve started reading your articles, I’ve seen countless mentions of MooTools, yet I’ve been in the dark; time to change this.

    Do you have anything you’d recommend to start me off?

  2. @Will: You should have mentioned this earlier! The more Moo, the better!

    I suggest starting with “Using MooTools For Opacity”. It covers some basic Moo usage. From there, move on to “Basic Ajax Requests Using MooTools 1.2”. Be sure to have the MooTools documentation open in another window.

    Moo is a lot of fun — go for it!

  3. MooTools is great! It’s my only choice at this moment. And it has great documentation.
    You can very easily extend it using your own classes and the framework itself is fully modular.

    It changed my life as a web-developper, I am very curious about its future.

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!