Modx 0.96 no more script.aculo.us?

Hi Folks!

I’m not sure if I’m getting this right: the new 0.96 uses no more script.aculo.us but mootools instead? I just updated and the pages that use some features of script.aculo.us don’t work anymore (no js loaded in header).

Now I wonder if I should switch to mootools or try to get script.aculo.us back to work...

I think my question should be rather simple to answer...

Quote from: Konsum at Aug 27, 2007, 05:06 PM

I think my question should be rather simple to answer...

It is and it isn’t, but it has been covered quite a bit in these forums lately.

The fact is, everyone prefers to work with a certain library, and these libraries are changing constantly. But nothing in the core of MODx is dependent on any specific library (other than in the manager interface), or if it is, it won’t be for much longer. All these dependencies you are talking about come from optional add-ons (even though many are distributed with the core). As we move forward, and the separation between core and add-ons becomes even clearer, it will be much easier to protect your installations from these library changes.

However, it will still be up to you to make sure the add-ons you choose do not conflict with each other or your site definition, as it is now.

I understand, thanks. But please take a look here: http://www.modxcms.com/features.html

MODx is the first free PHP CMS to offer an API that fully supports Web 2.0 Ajax technology thanks to script.aculo.us.

This quoute is taken from the features page...

Anyway, what would be the best and easiest way to get scriptaculous back to work? All the neccessary files should still be there, shouldn’t they?

Why should you need script.aculo.us when mootools (or jQuery) can do it better and faster ?

jQuery has a no conflict mode and mootools has a namespaced version distributed on the web, if using script.aculo.us along is an issue

Well, I don’t mind to use mootools. Can I use it out of the box within modx? Or what would I need to do?

BTW: The features page should be updated...

Yes the feature page should be updated, and we’re in the process of rewriting / creating a new template for the modxcms.com website... please be patient, we’re doing our best.

0.9.6 has been using mootools to power the backend, and QuickEdit has been entirely rewritten with mootools, but you can use any library you want to in the front end - provided you pay attention to library conflict issues. As I said, jQuery has a noconflit function (e.g [tt]var $j = jQuery.noConflict();[/tt]) and mootools has a namespaced distribution to avoid just that...

Thanks a lot!

As I understand, mootools gets loaded by AjaxSearch, which I use on my pages. So I won’t need to install anything, will I?