Forum Moderators: open
I've been really happy with Mootools, verging on evangelism. Whereas I used to give Javascript advice using raw built-in commands, I find increasingly I want to prepend statements with "first, get mootools. Then do it this way".
Valerio et. al. have have released a new version - v1.2 - which I admit I'm thrilled to learn about. Some keen new features added, and the object space has been reorganized in a way that makes a lot of sense.
But since a whole whack of objects and methods have been renamed, upgrading is not as simple as merely downloading the new mootools library. I'll have to go through all my code and refactor it. We're talking about nearly 15,000 lines of script... It's not something I have time to do, right now, but I do plan to tackle that project some time perhaps next month. Until time becomes available, I'll be sticking with version 1.11.
Since 1.2 is not backward-compatible with 1.11, they really ought to have called it 2.0. Someone in the mootools version numbering squad didn't quite figure out that semantic distinction between a major and minor version... but that's irrelevant pedanticum. The number doesn't really matter.
What has annoyed me is that they took the documentation for v1.11 offline.
I hit that documentation every single day. Many times a day. It's gotten more action in the past year than the dog-eared O'Reilly Javascript Guide sitting on my desk. I'll complain that moo's documentation wasn't fantastic; a lot of detail - sometimes important detail - was absent, and from time to time I'd actually have to crack open the uncompressed source to get the names of events, methods and properties. But it was there, and it was handy, like a huge cheat sheet.
And their documentation was sufficiently good that there are few bloggers who felt compelled to write about various Mootools methods; anything you had to say about using Mootools was usually covered by "RTFM", because the "M" was always just a click away. Search elsewhere for the properties available within the onSuccess event of an XHR object, and you'll see that Mootools commentation is a sparse hobby.
Now the 1.11 manual has gone offline, and I wish I had killed a few trees to print out a hard copy of the darned thing.
Please, moofolks, when you release a new build, version, or whatever, don't destroy the old one, just archive it off into a dark corner somewhere. Destroying all traces of the old version does not encourage us to upgrade, it just annoys us. Version 1.2 is very exciting, yadda yadda yadda. But some of us are going to be using (and building with) version 1.11 for a few weeks yet. OK?
http://docs111.mootools.net/ [docs111.mootools.net]
They have also provided Compatibility files which aid in the transition from 1.11 to 1.2,
the full story [blog.mootools.net]
