Which version of mootools should I use?

For anyone interested in running YUI Compressor themselves, here’s quick how-to:

1. Make sure Java 1.4+ is installed
2. Download YUI Compressor from http://www.julienlecomte.net/yuicompressor/
3. Browse to web\yuicompressor-2.2.5 (or whatever version you’re working with)
4. Place the JavaScript file you want to compress in this directory (e.g. uncompressed.js )
5. From command line, execute the following in the same directory:

(Optionally pass the --charset flag if you want to define your character set)

The required mootools functions for AjaxSearch are about a 42kb. 32kb with YUI compression
Compared to the 87kb of the complete mootools library, it could be interesting to download only these functions.
I will try to test the YUI version too and may be as an option propose this limited mootools pack.

For AjaxSearch js functions pack, for 6kb It’s useless.

On further consideration is anyone aware of any issues using the YUI compressor?

To get the YUI errors follows the link to the YUI JS Library and simply type "compressor" in the trackers search form (in the rigth upper side of the page). 6 bugs and 6 feature requests are currently opened.

The manager also uses Mootools for some TVs and possible the menu tree as well as possibly the Doc Manager module.

I agree with pixelchutes, it’s better to put the whole mootools library in MODx, if we want it... the choice is only between putting it all, or do not put at all...

Think about all plugins/snippets/chunks/effects that will come after the release of MODx 0.9.7, what if that snippet with "that beautiful menu effect" uses a mootools plugin that is not included with the MODx mootools? you should update it by hand, and are you sure that everything else remains compatible?

So, if the manager of 0.9.7 uses mootools, please put the whole 1.11 mootools inside the manager and compress it with YUI if you want.

We are talking about 50-100KB, not 100 MB!! and remember that the browser mantains a cache, so you have to download mootools only once per session!

@madmage,

The updated mootools library will actually be for the 0.9.6.2 branch.

0.9.7’s manager is actively being developed using ExtJS 2. (see http://www.extjs.com for more info)

Quote from: madmage at Jan 23, 2008, 11:46 PM

Think about all plugins/snippets/chunks/effects that will come after the release of MODx 0.9.7, what if that snippet with "that beautiful menu effect" uses a mootools plugin that is not included with the MODx mootools? you should update it by hand, and are you sure that everything else remains compatible?

It’s probably a bad idea to rely on anything in the manager directory for front end snippets in all reality. The manager and the front end are separate beasts, and changes to the manager for upgrades could very well negatively affect your front end work. For instance if we made the decision to go ahead and use mootools 1.2 or switch to jquery, you’d likely have problems if you were linking to the manager resources. If you have your own copy stored in your site assets directory, or wherever you prefer to store it, then the issue is avoided entirely.

We are only talking about about an extra 20-100KB, not 100 MB! Also keep in mind that the browser mantains a cache, so you have to download mootools/jquery/protaculous/insert-favorite-lib-here only once per session!

Quote from: rthrash at Jan 24, 2008, 10:44 AM

It’s probably a bad idea to rely on anything in the manager directory for front end snippets in all reality. The manager and the front end are separate beasts, and changes to the manager for upgrades could very well negatively affect your front end work. For instance if we made the decision to go ahead and use mootools 1.2 or switch to jquery, you’d likely have problems if you were linking to the manager resources. If you have your own copy stored in your site assets directory, or wherever you prefer to store it, then the issue is avoided entirely.

I agree: this is the best solution... anyway it is not the current solution, since quickedit relies on the mootools that resides in /manager/ directory... if in 0.9.7 the two "beasts" will be completely separated, it’s fine

Quote from: madmage at Jan 27, 2008, 06:52 AM

anyway it is not the current solution, since quickedit relies on the mootools that resides in /manager/ directory... if in 0.9.7 the two "beasts" will be completely separated, it’s fine

Indeed, but that is a simple problem with QuickEdit. Customize QuickEdit to rely on it from somewhere else, or create a custom QuickEdit interface using a library of your choice, or don’t use QuickEdit. It is just an add-on after all.

It would make sense to me that people would want different interfaces like this for QuickEdit if they plan on using other JS libraries on the front-end they are creating. Be nice to see a variety of QuickEdit’s contributed to the repository; one for each of the popular JS libraries.