There was a recent flurry of emails on the list discussing a conflict with the use of MooTools in conjunction with jQuery. When MooTools released v1.1, they renamed their events expando to $events, thus conflicting instantly with jQuery.
Well, Brazilian developer Alexandre Magno (http://blog.alexandremagno.net/) came up with a novel and quite simple solution to get around this issue; rename the $event expando in Mootools!
"I found a solution that works perfectly. Im the live example that we need sometimes to use the both frameworks. Im develop all my projects in jQuery, cause I learn more easily and feel more comfotable with it. Nothing to do with Mootools, with is a beatiful framework too... But I need the fancy upload to work and is just possible with Mootools, I make everything, but doesnt work because the conflict with the variable $event. I solve this issue by getting the mootools download with no compression, use a software like aptana, dreamweaver, or even notepad to replace all ocurrences of $event to $event2 for example, and compress the libraty after it. This way, the two frameworks works perfectly, since the use of jquery with noConflit its configured. I hope this works and soon I will develop this fancy upload for jquery to dont have to use both. Its a shame for the mootools team wait to Jquery solve this problem that noboby its blame... its just convention... why just simple replace $event for $mootoolsEvent or $mooEvent for example??? Somethimes its necessary use both, no doubt..""
This was posted in the MooTools forum in response to a post where John & I were trying to resolve an integration problem for a MooTools user who wanted to use MooTools and jQuery together. We realize that its unrealistic to expect that developers are going to use just one library and the team goes to great lengths to ensure some level of interoperability between other libraries via noConflict(). In jQuery v1.2, we take that a step further by allowing the renaming of the events expando to whatever you would like, thus avoiding any conflict.
While this was not a bug in jQuery, we feel strongly about allowing developers to leverage the tools that they need to do their work and we never want jQuery to be a bottleneck.
Thank you John & the jQuery team for continuing to make jQuery such a flexible solution and thank you Alexandre for expanding jQuery's reach to Brazil and offering up this great workaround.
> There was a recent flurry of emails on the list discussing a conflict > with the use of MooTools in conjunction with jQuery. When MooTools > released v1.1, they renamed their events expando to $events, thus > conflicting instantly with jQuery.
> Well, Brazilian developer Alexandre Magno > (http://blog.alexandremagno.net/) came up with a novel and quite simple > solution to get around this issue; rename the $event expando in Mootools!
> "I found a solution that works perfectly. Im the live example that we > need sometimes to use the both frameworks. Im develop all my projects in > jQuery, cause I learn more easily and feel more comfotable with it. > Nothing to do with Mootools, with is a beatiful framework too... But I > need the fancy upload to work and is just possible with Mootools, I make > everything, but doesnt work because the conflict with the variable > $event. I solve this issue by getting the mootools download with no > compression, use a software like aptana, dreamweaver, or even notepad to > replace all ocurrences of $event to $event2 for example, and compress > the libraty after it. This way, the two frameworks works perfectly, > since the use of jquery with noConflit its configured. I hope this works > and soon I will develop this fancy upload for jquery to dont have to use > both. Its a shame for the mootools team wait to Jquery solve this > problem that noboby its blame... its just convention... why just simple > replace $event for $mootoolsEvent or $mooEvent for example??? Somethimes > its necessary use both, no doubt..""
> This was posted in the MooTools forum in response to a post where John & > I were trying to resolve an integration problem for a MooTools user > who wanted to use MooTools and jQuery together. We realize that its > unrealistic to expect that developers are going to use just one library > and the team goes to great lengths to ensure some level of > interoperability between other libraries via noConflict(). In jQuery > v1.2, we take that a step further by allowing the renaming of the events > expando to whatever you would like, thus avoiding any conflict.
> While this was not a bug in jQuery, we feel strongly about allowing > developers to leverage the tools that they need to do their work and we > never want jQuery to be a bottleneck.
> Thank you John & the jQuery team for continuing to make jQuery such a > flexible solution and thank you Alexandre for expanding jQuery's reach > to Brazil and offering up this great workaround.
> There was a recent flurry of emails on the list discussing a conflict > with the use ofMooToolsin conjunction with jQuery. WhenMooTools > released v1.1, they renamed their events expando to $events, thus > conflicting instantly with jQuery.
> Well, Brazilian developer Alexandre Magno > (http://blog.alexandremagno.net/) came up with a novel and quite simple > solution to get around this issue; rename the $event expando inMootools!
> "I found a solution that works perfectly. Im the live example that we > need sometimes to use the both frameworks. Im develop all my projects in > jQuery, cause I learn more easily and feel more comfotable with it. > Nothing to do withMootools, with is a beatiful framework too... But I > need the fancy upload to work and is just possible withMootools, I make > everything, but doesnt work because the conflict with the variable > $event. I solve this issue by getting themootoolsdownload with no > compression, use a software like aptana, dreamweaver, or even notepad to > replace all ocurrences of $event to $event2 for example, and compress > the libraty after it. This way, the two frameworks works perfectly, > since the use of jquery with noConflit its configured. I hope this works > and soon I will develop this fancy upload for jquery to dont have to use > both. Its a shame for themootoolsteam wait to Jquery solve this > problem that noboby its blame... its just convention... why just simple > replace $event for $mootoolsEvent or $mooEvent for example??? Somethimes > its necessary use both, no doubt..""
> This was posted in theMooToolsforum in response to a post where John & > I were trying to resolve an integration problem for aMooToolsuser > who wanted to useMooToolsand jQuery together. We realize that its > unrealistic to expect that developers are going to use just one library > and the team goes to great lengths to ensure some level of > interoperability between other libraries via noConflict(). In jQuery > v1.2, we take that a step further by allowing the renaming of the events > expando to whatever you would like, thus avoiding any conflict.
> While this was not a bug in jQuery, we feel strongly about allowing > developers to leverage the tools that they need to do their work and we > never want jQuery to be a bottleneck.
> Thank you John & the jQuery team for continuing to make jQuery such a > flexible solution and thank you Alexandre for expanding jQuery's reach > to Brazil and offering up this great workaround.
Well, in the interest of full disclosure, for those that don't know, Olmo is part of the MooTools development team.
Now, back to the topic. If there's nothing to glean and there's no benefit in sending list members to what ended up as a very unproductive discussion, why would it be the right thing to do?
Olmo wrote: > There's nothing to glean. It's the right thing to do. > -Olmo M.
> On Aug 31, 9:23 pm, Rey Bango <r...@iambright.com> wrote: >> Actually, I didn't. I left it out intentionally as there was nothing to >> be gleaned from the thread.
> Well, in the interest of full disclosure, for those that don't know, > Olmo is part of theMooToolsdevelopment team.
> Now, back to the topic. If there's nothing to glean and there's no > benefit in sending list members to what ended up as a very unproductive > discussion, why would it be the right thing to do?
> Rey... > jQuery Project Team
> Olmo wrote: > > There's nothing to glean. It's the right thing to do. > > -Olmo M.
> > On Aug 31, 9:23 pm, Rey Bango <r...@iambright.com> wrote: > >> Actually, I didn't. I left it out intentionally as there was nothing to > >> be gleaned from the thread.
Thanks. That helps out quite a bit. Kind of like I did when I posted in the MooTools forum. Its always good to let people know where you're coming from.
> I don't need to waste my time in trying to lecture you. Should have > known better.
> Thanks. That helps out quite a bit. Kind of like I did when I posted in > the MooTools forum. Its always good to let people know where you're > coming from.
> > I don't need to waste my time in trying to lecture you. Should have > > known better.
I am facing this problem... yes, its because mootool+jQuery. My Joomla site's Template system runs on mootool, but my one of the component runs on jQuery.
So, I need to do this Hack.
My question is -
If I convert '$event' to '$event2', will it effect on the workings of the template system ?
> I am facing this problem... yes, its because mootool+jQuery. > My Joomla site's Template system runs on mootool, but my one of the > component runs on jQuery.
> So, I need to do this Hack.
> My question is -
> If I convert '$event' to '$event2', will it effect on the workings of > the template system ?
I am sorry to repost again about this conflict, but I am still having the conflict beetween this two frameworks. I would like to say that I LARGELY prefer jQuery, which makes me able (just a graphic with NO coding skills...) to add utilities and effects to my site in a breeze (thanks, really)! But I have to make sites where other devs use Mootools, so I am still encountering the issue. I update the jQuery package to the latest, since I red that it was solved, but the conflict is still there. Thanks to everyone which will have the time to help me. The following is the link where I get the issue: http://www.bonsai-studio.net/clients/clickadvisor-02/plugins-pages/ac...
|
