Matteo Pelucco ha scritto:
Grégory Joseph ha scritto:
Hi Matteo,
Feel free to propose patches for this, it'd be a welcomed fix. We
currently have a project that uses jquery without any problem, but
most likely because it uses the jQuery.noConflict(); function to avoid
this.
I think so, one of jQuery benefits is the "namespaced" feature.
MooTools is not scoped, as Prototype and other frameworks.
I will work to solve this issue and I will propose my solution (if I'll
found it ;-) )
A quick and dirty workaround is to use <cms:link /> BEFORE MooTools core
script.
MooTools will automatically redefine the $ function and in this way all
MooTools script will run.
The side effect is that the entire Magnolia GUI run using MooTools $
function: in my opinion it is not dangerous, because MooTools $ function
is cross browsers and if Magnolia doesn't use it for advanced feature
but only for returning
document.getElementById('myId');
there should be no problems at all.
What do you think about it?
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
