If you don't have a lot of Prototype code, and that's within your
control...you should be able to convert your existing prototype code
to jQuery syntax, then get rid of Prototype entirely. We looked at
doing this when we started mixing jQuery into our code, but we had WAY
too much Prototype to
Hi dizzyjay,
the noConflict function works great, but the problem I think is that
you rename the jquery object, so all other developper will have to
change there scripts to no use anymore the $ function (by defaul
$==jquery).
some times ago, a protosafe library was developped, but it has
This is completely theoretical, and probably even more ludicrous as I
think of it being plausible cross-browser...
But in theory if you did something like this
var A = function(){ alert(First definition);}
A();
var A = function(){ alert(Second definition); };
A();
Would behave as such, so
Not sure I quite understand the suggestion (please explain). If I end
up revisiting the jquery code, I'll probably just use the
jquery.noConflict() function and reassign the embedded jquery $()
refernces to something different. Too bad I can't do the same with
the prototype code; there's a lot
Thanks- this looks like what I'll need to do. Hopefully the portal
owner will be accepting of the change. Too bad prototype doesn't have
the same conflict workaround (it would be much easier for me to
change).
cheers,
\\dj
On Feb 6, 11:22 am, david david.brill...@gmail.com wrote:
Hi
