Articles by ‘Arian Stolwijk’

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.


MooTools Core 1.3.2 and More

Written By Arian Stolwijk, on Thursday, April 28th 2011, 3:23pm

Today we announce the simultaneous release of MooTools Core 1.3.2 and More This is mostly a bugfix release and does not contain many new features. The most important fix is within our selector engine, Slick, which failed in some cases where the selectors began with an operator (ex. ~div).

A new component has been added to MooTools More: Table. Table was slated to be added in MooTools Core 2.0, but we’re making it available in MooTools More now. Table is similar to the JavaScript object literal, but where an object can only have a scalar value (string or number) as a key, Table can have any value as a key. Where the order of values in an object is not static like an array (by specification, usually browsers keep the order which they are defined), the values in Table will have a static order. These advantages come with a performance cost, where an object value is a direct look-up, Table uses indexOf which is less efficient, so use with care.

Notable changes in MooTools Core include:

  • Fixed Slick bug with ~div-like selectors
  • Fixed MooTools in the Node.js environment
  • Fixed an exception in DOMReady in Chrome when the page with MooTools was in an IFrame
  • Fixed setOpacity for very small numbers in IE
  • Fixed an exception in FireFox 4 when MooTools tried to overwrite document.head
  • Added the possibility to create elements with boolean values with an selector, e.g. new Element('input[checked]');

MooTools More:

  • Rewritten Element.Position which solved some issues
  • Added Table, as described above
  • Ironed out some Event Delegation issues
  • Additional fixes can be found at the Lighthouse for

Get it!

Events with MooTools - Element, Class, Delegation and Pseudos

Written By Arian Stolwijk, on Monday, March 28th 2011, 2:18pm

One of the most useful and common part of MooTools is its Events Type. There are two Event usages: Element and Class. Element.Events is probably the most known because that’s probably one of the first things you’ve used when you started using MooTools. Furthermore, MooTools More 1.3 Events.Pseudos has been introduced to give even more power and control over Events and with Event Delegation can give your page a massive performance boost. This blog post will give you a deeper insight into all components.


MooTools Survey Results

Written By Arian Stolwijk, on Monday, January 31st 2011, 2:32pm

Last month we held the MooTools User’s Survey and we would like to thank you all for participating and sharing your ideas. We received more than 700 submissions! Here is a summary of the results and our thoughts about them.


Most of you think MooTools Core is fine as it is, with an obvious exception: Swiff has to go. This change has already been planned for the next major release. There are several good ideas about what we could add to Core: element shortcuts (.hide() and .show(), for example), a few Types from MooTools More, Event Delegation, Pseudo Events, and cowbells! In short, we would like to keep MooTools Core a compact, modular, object oriented framework. Specific UI plugins, for instance, would be a better fit for MooTools More or maybe the Forge.


Many of you supplement MooTools Core with MooTools More (96%) but are also equally divided whether More should contain UI plugins or if those should be in the Forge. Most of you (60%) like to see more abstraction APIs, such as enhancements to Core. That’s probably why Types and Drag are the most popular More components. HtmlTable is the biggest candidate for removal (43%) followed by Accordion (34%) (ndVP: yey!). In general, you had many ideas about what to add to MooTools More, such as specific UI plugins, support for HTML5 features, geolocation, and storage.


The Forge is pretty popular, about 65% of respondents use the Forge to a find plugin. About 11% have contributed to the Forge with new plugins. Respondents shared great ideas for improving the Forge, including: comments, ratings, better search, featured plugins or a combined (packager-web) download page which selects all dependencies.

API Documentation

A very important part of MooTools is the online API documentation. Most of you think they are pretty good, but are also put off by the lacks of examples. We’ve heard you and that’s why we responded with our fancy new demos which we released a few weeks ago! Our plan is to add new demos which we will use as additions to the docs. You will find links from the docs to the demos, which you can play with thanks to the jsfiddle integration. We don’t have demos of each part of Core or More yet, so if you want to help, you can fork the repository and add new ones, or just ping us (@astolwijk or @fakedarren) with new jsfiddles. Another popular idea that we particularly liked is the addition of a comment system to the API documentation.

I’d like to point out that you can easily start hacking on the docs if you feel so inclined. Just make sure you have a github account, fork mootools-core or mootools-more, browse to the Docs folder and select a .md file. Github has awesome online editing features, so you can work without knowing anything about GIT! If you modify a file we will see it via the network view and will include your fix into the main repository.

Upgrade to MooTools 1.3

We are really happy to see that the release of MooTools 1.3 went smoothly and most of you are already in love with the new MooTools. One point for improvement would be to put the upgrade tutorials on the wiki in a more prominent place on the website.

The lucky winner of the T-Shirt

Congratulations to the lucky winner of the awesome MooTools t-shirt. You’ll receive it shortly, and we sincerely hope you’ll wear it with pride!

In conclusion, thanks for all the “MooTools FTW!” responses, the cowbells suggestions, and other great feedback you guys sent us. We <3 you.

MooTools Survey

Written By Arian Stolwijk, on Sunday, December 5th 2010, 5:50pm

MooTools Shirt

The community and the MooTools users are very important for MooTools and its development. Therefore we would love to hear who you are and how you are using MooTools. You could do this by this survey. It will take about five minutes and none of the questions are required.

The purpose of this survey is to help us prioritize what the development team spends its time on. We want to make MooTools as useful for you as we can. Some questions are more explicit than others, relating to where we put things or what features we should focus on more or less. Armed with this information we can dedicate our resources to the things that matter most to you.

Because we think your opinion is valuable, we’ll be giving something in return. You can win a MooTools™ Shirt. Maybe you will look just as awesome as Tim soon!

The survey will be open for two or three weeks. After that time we will compile some sort of conclusion from the results and share it with you.

So head over to the survey and let your opinion count!

Update: I’ve just closed the survey. A huge thank you for the awesome responses!