Mootools home page

I just noticed that on the main MooTools page there is a list of applications using MooTools, including joomla. Has anybody contacted them about adding MODx to the list?

Susan,

Not that I am aware of.

I’ll drop the admin a line but if someone could provide me some details as to when Mootools was added to the package and why we replaced what was there with Mootools. If we had an approximate download number since Mootools was added that too would be helpful.

Cheers and all the best,

Jay

I believe MooTools was added when 0.9.6 was released. Scratch that, it was used in 0.9.5 already for the menu at least. Previously Scriptaculous and prototype was used in MODx manager. Don’t know the exact reasons, but it was at least a lot faster than Scriptaculous+prototype combo that was previously used. Someone with better knowledge / memory can shed more light on this.. Count the downloads from 0.9.6 0.9.5 onwards.

Thanks doze. That should suffice.

It might be worth noting that Mootools is not used at all in Revolution and beyond.

No, but it’s used in Evolution.

Quote from: sottwell at Jul 29, 2008, 08:16 AM

No, but it’s used in Evolution.

Sure, just saying; we don’t want to lead the guys at MooTools on that we’ll be continuing to use their product in our future versions. I’m all for getting our name with them, but it should be clear it’s for a legacy product by us.

I think when the Evolution word gets out, things will be way clearer about the Evolution / Revolution distingo.

Still, my understanding was Evolution will keep an active status (e.g regular upgrades, even if incremental ones) and as such maybe we should find an alternative term to "legacy" which might have a "dead product" connotation. During the transition phase (that’s for us experienced Evo users - we need to get used to Revo before actually jumping to it), many people will keep Evolution to run their website and some might never need to make the jump. Alternatively, some people (my guess is mostly devs) will go straight to Revolution because it opens so many new doors for them

Anyway, we can be listed @mootools, can’t hurt. As long as we’re clear that templates are the tie between MODx and frontend use of mootools (and not MODx core code), which means everyone is free of choosing its js framework (I for one use jQuery). In a way, we’ll probably get listed @extJS even if people are free to build a Revolution manager with another framework (if I understand correctly this will be possible).

My thought was that the Manager uses MooTools extensively, so that does make us a CMS that uses MooTools.