Avoid jQuery conflicts

[sehmaschine]

see http://learn.jquery.com/using-jquery-core/avoid-conflicts-other-libraries/

Not sure what's the best way to achieve this – django uses:

(function($) {
})(django.jQuery);

[gregmuellegger]

To be honest, the django approach always bugged me. I always wanted to have a jquery in the admin anyway. And I think it's nonsense to include two different versions (one for your own plugins and the django.jQuery one for the django stuff). I think we should always include the latest jquery version without any noConflict calls.

If a user needs his own jQuery, then he can use the noConflict himself.

The only problem I see is that custom widgets might define jquery as dependency in their class Media: listing. If that one gets included, it will break the already included jquery from admin2. But that problem isn't solved by using noConflict for the admin itself. Because if you then have two different widgets with each importing jquery .... you see the big picture.

I want a JS dependency resolving in django anyway. Isn't their a good app for this anywhere?

[sehmaschine]

Theoretically speaking I do agree, but ... when using 3rd–party admin–based apps, you probably cannot assume they use noConflict. Besides, if an admin–app uses django.jQuery it's pretty clear what they refer to.

[douglasmiranda]

I'd agree with @gregmuellegger, but @sehmaschine has a point when saying that we cannot assume they use noConflict.

I've researched a lot about this. And looks like, still, the best way to do this is:

(function($) {
    //...
})(django.jQuery);

Maybe we should to encourage the developers to use noConflict from now on. So, in the future, the reality doesn't sucks.