Comments on: The MooTools 1.3 Upgrade Path

By: Aaron N.

Aaron N. — Tue, 31 Mar 2009 15:34:58 +0000

There is not a public roadmap for MooTools currently.

By: asvanu

asvanu — Tue, 31 Mar 2009 09:07:27 +0000

where is MooTools roadmap?

By: Dan

Dan — Thu, 19 Feb 2009 18:29:46 +0000

I’ve said it before, and i’ll say it again. If you break backwards compatibility, don’t just increment the minor version, but the main version. In other words: call it 2.0 (you should have done that with 1.2 already).

Just my 2 cents….

By: Aaron N.

Aaron N. — Thu, 29 Jan 2009 16:30:02 +0000

I think the general thinking behind moving Hash and Swiff (and Cookie) to m-more is that these things are not required in order for the Core to work. The same could be said about Request and Fx, but these are really at the heart of what MooTools is for – enabling dynamic interfaces. Hash on the other hand is useful, but frankly so is the native object in JavaScript.

I like Hash, but it’s not like I don’t build my own version of the library every time I use it…

By: Morganizeit

Morganizeit — Thu, 29 Jan 2009 11:55:37 +0000

No issues for me with the renaming of the $functions, it’s a simple remap.

A good argument for leaving Hash in core is the disruption to pulling the base library from the google code service. Folks already using core from the service plus Hash in their code would potentially have to add another request, though I guess they could also patch the Hash module into their own script. As others have pointed out, Hash is more generally useful than Swiff or others staying put in the core… would a mt developer provide more detail about why it makes sense to move Hash but not others?

Nutshell: Ain’t broke. Don’t fix it.

By: Tim Lund

Tim Lund — Wed, 28 Jan 2009 23:13:02 +0000

Hehe and Indeed I am.. But I just think it deserves a spot in core

By: Aaron N.

Aaron N. — Wed, 28 Jan 2009 20:14:28 +0000

Hi Tim, First, note that you can download $E from my libs (download). But yes, the goal is to make the upgrade from 1.2 to 1.3 much easier than 1.11>1.2 was.

By: Tim Lund

Tim Lund — Wed, 28 Jan 2009 18:03:23 +0000

Love the idea of putting these functions where they belong. But my biggest hope for 1.3, and perhaps even 1.4, is compatibility. We create Typo3 sites where I work, and one of our problems is that there’s still alot of extensions using 1.1. I myself write all my code in the newest version and that usually leads to headaches and bosses breathing down my neck :)

I know it isn’t easy for innovators when they can’t change something they over time found out was the wrong way of doing things, but please make the transition as smooth as possible :)

@Matias N

Would like $E back as well :)

By: Roberto

Roberto — Tue, 27 Jan 2009 10:17:41 +0000

Congratulations for your page and efford. The book is very good too.
I use mootools and the only sorrow is that the official page of Mootools is ugly and poor (the demos is a shame) – I can say this because I use and love Mootools – (others can’t!).

By: Daniel Buchner

Daniel Buchner — Mon, 26 Jan 2009 06:23:41 +0000

Psssst! If you want CDN-like ability to host Mootools More or any of your other code that is not in the Goog lib selection, just open a Google Code Hosted project and upload your files then like to them there. Shabam! Instant awesome!