Inspired by [-Stash-]'s jQuery extension, this extension wraps up all the various Mootools components that any of your installed extensions need, puts it in one file, packs it, then puts it at the top of any extension-added javascripts.

This means that you no longer have 5 extensions all adding their own mootools libraries to each page resulting in a 200kb download for each user. Instead you have one, small mootools.js sitting at the top, ready to be used by any javascript files that follow it.

It packs the minimum amount of components, just enough so that every extension should work perfectly without bloating page load times. It also dynamically finds which components are needed on each page and will only load those so that you don't have a thousand lines of unused javascript framework sitting in the page's header.

Once you install this, make sure you make the Mootools/cache folder writeable. Use chmod 777 if you're not sure.

Extensions that use this
Live Discussions
Collapsible Panel
User Info
System Message

Note: These extensions do not require this one however it is highly recommended that you use them in conjunction with this for increased compatibility and performance.

Developers
All you have to do to make your extension use this is something like the following (taken from the User Info extension):

if(!function_exists('MT_AddComponent')) {
	$Head -> AddScript('extensions/UserInfo/mootools.js');
} else {
	MT_AddComponent('Tips', 'Element.Selectors');
}
$Head -> AddScript('extensions/UserInfo/userinfo.js');

First, make sure the function exists. If not then load your backup mootools.js file. If it does exist then just pass it a list of the Mootools components you need (as seen on the Mootools download page). The script will handle any and all dependencies so you only have to list the bare minimum components.

Hey Presto! 'userinfo.js' will have the Mootools library at its disposal and so will any other extension's javascript if it needs it.

A Word of Warning
Some extension's javascript files are a tad incompatible with Mootools. Not to name names or anything but YellowFade's 'functions.js' effectively kicks Mootools' Window.DomReady event in the face. To remedy this, the script relegates function.js to the bottom of the script list so it gets called last. This means that Window.DomReady and the YellowFade effect both work.

There will be other cases like this so, if you find any, don't hesitate to contact me and I'll attempt to fix them.

Compatibility
Special code has been written within the Mootools extension to ensure that the following extensions work with this one:
Yellow Fade
Smooth Page Jump
Discussion Tags
Low-Cal Vanilla
Page Manager

Credits
Mootools, it's cute and loveable
Dean Edward's Packer, the PHP 4 version because not everyone has PHP 5

Uploaded version 1.2 of Mootools.

Uploaded version 1.3 of Mootools.

Uploaded version 1.4 of Mootools.

It takes a page refresh for Mootools to force itself to the top of the extension list. Other than that I can't see what would be the problem. If you only need Fx.Slide, Window.DomReady and Element.Selectors then all you need to do is call:
MT_AddComponent('Fx.Slide', 'Window.DomReady', 'Element.Selectors');
All the dependencies will be added automatically. Also, it shouldn't matter which order you list them in.

Uploaded version 1.6 of Mootools.

It's much smaller as of 1.7 because I cut out all the cache files that were left over from testing. I've modified my build script so that it shouldn't happen again.

It still uses them, yes. What I meant was that it was generating files and putting them in the cache while I was testing. When I built the extension, it copied those files into the extension archive so it had a bunch of unnecessary files that were using up space.

Yup, I ran into your above error when I did a local install. I've added a section to the readme about making the cache folder writeable now.

I don't think Collapsible Panel ever had [+] or [-] icons. Might add it to the to-do list though although it might inhibit support for other themes.

Heh, I'm really glad to finally be rid of that bug. Ø had had it for ages and I spent so long trying to fix it. The worst part is that, in order to fix the bug, I had to type one extra character... an '&' to be specific. The problem is that I think you're using PHP 4 and I was testing on a PHP 5 server which meant that objects behaved slightly differently. I was passing the $Head object by reference (as opposed to by value) throughout the Mootools class but I forgot to pass it by reference in the delegate function. That's ok for PHP 5 which passes objects by reference by default but for PHP 4 you have to explicitely tell PHP to do that.

And as a bonus, I also found out why the extension was so huge (after going over the 198k limit). I cleared out the cache folder which unluckily caused your cache issue.

I might get a rest now...

Uploaded version 1.8 of Mootools.

After you updated it the issue I was having with my extension (Hidden Text 2) is now gone as well.

Could be. It did mention prototype.lite.js which is included by the Smooth Page Jump extension. Mootools is supposed to remove this and replace it with a Mootools version. I think Mootools is setup to remove those scripts if it's on the search or comments page. I think perhaps with BlogThis, Smooth Page Jump is being loaded on a different page. It should just be a matter of adding the new page to the if statement.

@Krak: Yeah, I'm guessing Hidden Text 2 used a bit of javascript. If there are any errors with any of the javascript scripts then usually none of the rest will work either.

Uhm nope, it's never been reported before. Are you only getting this error with this extension or are there others?

umm, Fyorl seems to be missing... :(

help!

nevermind. i found the problem. in the conf/extensions.php folder there was only one line=
"include($Configuration['EXTENSIONS_PATH']."Mootools/appendix.php");"

deleted that and it was fine, but i lost all my extensions settings, so now i have to reinstall them and make sure extensions.php is working properly.

anybody knows why this happens?

Is there anybody smart out there who has at least an Idea to solve this problem?

I looked a bit at the code but didn't discover where the appendix line was added :S

Yes, but you almost never hear the positive feedback, only the negative.

I use it and it works just dandy!

Unfortunately the same happens at a decent PHP5 webhost!

Any advices?

Thanks,
Zen