I’m heading off to Boston to attend An Event Apart tomorrow and I’m pretty excited about it. I’ve never been to anything conference like before and so I’m really not sure what to expect but I am hoping to meet some good people while listening to informative talks about the stuff on the web and the parts of web development that really interest me.

I’m sure I’ll have more to say about it once I’m there and in the thick of things so that is all for now. Bags packed ready to travel.

This is not a big landmark in the history of MooTools by any means but it means a lot to me. I just put what I hope to be the finishing touches on the first of what should be many Classes I’ve written for MooTools. It’s not a terribly exciting or complex piece of code I think I just see it this way because it is really my first foray into providing some contribution besides a very little bit of knowledge and advice to an open source community.

The source is viewable at my plugins repository on GitHub and I certainly plan to continue to add more Classes as well as BDD specs and proper demos for them.

One down; many, many to go.

My favorite javascript framework has come out of beta into a final. The release of MooTools 1.2 brought about a whole slew of changes and not just to the code base. The Moo team split made a number of API changes to make the library more usable and more consistent. The team has also separated the project into ‘core’ and ‘more’. MooTools Core is, as expected, the heart and soul of the framework, it contains the classes and functions the rest of MooTools is built upon. MooTools More on the other hand is akin to officially sanctioned plugins.

In addition to API changes and the separation of core and more the MooTools team has moved from a Subversion repository to Git. Both core and more have their own GitHub repositories (mootools-core and mootools-more respectively). Of course without Subversion Trac loses a lot of it’s appeal and so they have moved their defect tracking over to Lighthouse which provides some Git/GitHub integration through plugins (called beacons).

I’ve been working with the 1.2beta for quite some time but even the beta to the final had a number of changes (mostly shortcut methods were removed) so there will still be some adjustments. All in all though I’m pretty excited about all the changes and what it means for things moving forward. In fact I’m so excited about it I’ve created my own fork of the mootools-core and begun tinkering around with the source. I’m also hoping to get a little more involved in the project rather than just being a faithful user. So here’s to the bright future of a great library.