Okay, so it's simple, and it's not advised to mix libraries. However,
the documentation is still confusing as heck - just thought I'd like
someone know.
On Jun 5, 2:29 pm, Ricardo wrote:
> jQuery saves the '$' object on init, if it exists. noConflict()
> 'returns' it to the old owner. Passing tr
I agree with waseen
2009/6/5 waseem sabjee
> to be honest. it would not be wise using multiple different js libraries.
>
> you basically have multiple definitions that do the exact same thingit
> really is best to stick to a specific library as much as you can.
>
>
> On Fri, Jun 5, 2009 at 8
to be honest. it would not be wise using multiple different js libraries.
you basically have multiple definitions that do the exact same thingit
really is best to stick to a specific library as much as you can.
On Fri, Jun 5, 2009 at 8:29 PM, Ricardo wrote:
>
> jQuery saves the '$' object o
jQuery saves the '$' object on init, if it exists. noConflict()
'returns' it to the old owner. Passing true the 'jQuery' object is
also freed. There's not much to it:
jQuery.extend({
noConflict: function( deep ) {
window.$ = _$;
if ( deep )
it's like namespace faking
var $myvar = JQuery.noConflict();
$myvar(function() {
$myvar("body").animate({ opacity:0}, 500);
});
On Fri, Jun 5, 2009 at 5:06 PM, Alex Ehlke wrote:
>
> The online documentation for jQuery.noConflict() seems to be
> incorrect, or ambiguous at best. Here is the te
5 matches
Mail list logo