Confliction javascript: moo.js and moo.fx.js

I’m only capable of copying other peoples hard work, so now I’ve gotten a conflict I’m not able to solve.

I use moo.fx.js for ajaxmenu and quickedit. I also want to use image preloading which requires moo.js the way I’ve found how to do it (similar to the beautiful header images Scotty has over at scottydelicious.com.)

If I load moo.js at the very end (after moo.fx.js) image preloading works but breaks havoc on ajaxmenu and quickedit.

If I load moo.fx.js at the end (which quickedit always does) ajaxmenu and quickedit works fine, but image preloading don’t work.

Anyone knows how I can solve this conflict? I guess they are both part of the same codebase (Mootools), where moo.fx.js is a subset of the functionality of moo.js, so I have hope that they can coexsit or that I can replace moo.fx.js with moo.js somehow.

Ajax for teh win

TJ

Grab the 096 RC and use the all-mootools versions there.

Ah.. I’ve just been reading up on that, and it seems a bit too unstable at the moment. I use manager and permissions extensively, and my editors are dependant on quickedit, so I think I’ll have to wait for a more stable version.

In the meantime, the only thing I need from mootools (and that moo.fx.js) is this function: http://p.caboo.se/44372
It creates the image preloading effect you can see over at http://www.scottydelicious.com/

So if anyone can convert that function to prototype / scriptaculous for me I’ll be just as happy

Permissions are the same as what was encountered previously I think. At least according to Jared.