Articles in the ‘All’ Category

MooTools Core 1.4.1

Written By Christoph Pojer, on Thursday, October 6th 2011, 2:01pm

Today we release MooTools Core 1.4.1 which is a small maintenance release and as such only fixes bugs that were introduced in previous releases. We have fixed the mousewheel event in Firefox, Element.fade sets the visibility CSS-property again, Event.Delegation now behaves properly if you use fireEvent and we have fixed a couple of issues with Element.setProperty and Element.removeProperty.

Upgrading from 1.4.0 should not cause any backward incompatibilities. We recommend all users to update to 1.4.1 as soon as possible.

Get it!

MooTools 1.4.0

Written By Arian Stolwijk, on Saturday, September 10th 2011, 9:16am

As of today a new version of MooTools is available. This includes MooTools Core and MooTools More. We’ve communicated a lot about changes for 2.0 but we also felt we had some good stuff that would benefit you directly which we wanted to add to the 1.x releases. This good stuff contains of course numerous bugfixes but mostly one important new feature for MooTools Core: Delegation. This 1.4 release should be fully backward compatible with the MooTools 1.2 and 1.3 series’.

So all changes for 1.4.0:

  • Move Delegation into Core.
  • ECMAScript 5 compatibility fixes. Among them are Function.bind, Array.map and String.trim
  • Deprecate Element.setOpacity() and Element.set('opacity'). Element.setStyle('opacity') is the only correct way now (the same applies for getters).
  • Disable the 1.2 compat layer by default in the builder.
  • Revamp Element.getProperty, Element.setProperty. Element.getProperty uses Slick.getAttribute now to share this code and save some bytes.
  • IE7 doesn’t crash anymore when cloning an element twice.
  • The Selectors documentation is back and updated for Slick.
  • Update Slick to 1.1.6
  • Unified change event behavior across browsers.
  • Renamed Event to DOMEvent so it will not conflict with the native Event object.

Event Delegation

Event delegation is a common practice where an event listener is attached to a parent element to monitor its children rather than attach events to every single child element. It’s more efficient for dynamic content or highly interactive pages with a lot of DOM elements.

Example

var myElement = $('myElement');
var request = new Request({
    // other options
    onSuccess: function(text){
        myElement.set('html', text); // No need to attach more click events.
    }
});
// Adding the event, notice the :relay syntax with the selector that matches the target element inside of myElement.
// Every click on an anchor-tag inside of myElement executes this function.
myElement.addEvent('click:relay(a)', function(event, target){
    event.preventDefault();
    request.send({
        url: target.get('href')
    });
});

MooTools More

  • Removed Delegation. It’s now in Core obviously.
  • Added the length validator to Form.Validator
  • Added the update method to HtmlTable which let you update rows
  • Added ARIA accessibility to Tips.

If you’d like to know what exactly changed, checkout the compare view.

We would like to thank everybody who has contributed code, documentation fixes and ideas to make this release possible. Among them are arieh, Delapouite, madisvain, adamnbowen, mooyah, GCheung55, amadeus, rasmusfl0e, jasonwaters, realityking, Nico-B, mcfedr, donatj, csuwldcat, ibolmo, cpojer, kamicane, timwienk, fakedarren, anutron, subtlegradient and myself arian.

Bugs

Thanks to GitHub contributing is easier than ever. It’s very easy to fix them or to report them, especially since we moved to GitHub for our issues. Bugs can reported on the MooTools Core Bug Tracker and for MooTools More you can go to the More Bug Tracker.

If you have any questions, either about how to do something or about contributing you can ask, or something to share, just join the MooTools Mailing list or IRC (#mootools on freenode.net). We have an office hour each Tuesday but you can hang out there whenever you want.

Get it!

Moving to GitHub Issues

Written By Arian Stolwijk, on Monday, August 1st 2011, 7:14pm

We at the MooTools headquarters love GitHub for all its features which makes contributing and managing our code much easier than say, five years ago. GitHub is the place to be for all cool JavaScript projects which makes following your projects of interest a lot easier. When we moved to GitHub a long time ago, the ticket system was too basic to be a real solution. Fortunately this has since improved.

Especially the additions for milestones and assignees were important for us. With this in place GitHub issues can finally replace Lighthouse.

The main advantages are:

  • Everything at one place, one login
  • Easier to follow MooTools
  • Similar to pull requests

A disadvantage is that most of the current issues are in Lighthouse. Darren did an awesome job going through a lot of them but there are still some open or not fixed. A proposed option was to move all tickets to GithHub, but we decided to try to address as many as we can and just move on to GitHub.

Now every MooTools project has its issues on GitHub:

So if you know anything about any of the issues at GitHub or some old Tickets at Lighthouse, comments and fixes are highly appreciated!

July 12th Dev Hour Recap/Summary

Written By Olmo Maldonado, on Tuesday, July 19th 2011, 9:28am

Every week the MooTools developers host an IRC OfficeDeveloper Hour where they work together to listen to your feedback, answer your questions, and develop MooTools. We do this every Tuesday at 11am EST at #mootools Freenode IRC Channel. Everyone’s welcomed to join us.

This recap includes:

  • Mentions
  • Answers to: Where do you guys think MooTools can improve?
  • Sneak Peak to Improved Docs
  • Agenda for July 19th Dev Hour

    (more…)

July 5th IRC Office Hour Recap/Summary

Written By Olmo Maldonado, on Monday, July 11th 2011, 2:11pm

Every week the MooTools developers have an IRC office hour meeting where they work together to listen to your feedback, answer your questions, and develop on MooTools. We do this every Tuesday at 11am EST at #mootools Freenode IRC Channel. Everyone’s welcome so join us tomorrow.

This recap includes:

  • Compare 1.3.x and Experimental 2.y.x Code Diffs
  • Things to Come (Agenda’ed Office Hour, Dedicated “Hackathon” Office Hours)

    (more…)