Yeah, I guess you're right, I should have put the Class to Wicket
namespace. Can you open an issue for it, please?
-Matej
Caleb Land wrote:
I'm using MooTools (http://www.mootools.net) library in my Wicket
1.3application and there is a collision between the Wicket Class
in wicket-ajax.js and the MooTools Class. Basically, any MooTools code
that's executed before the wicket-ajax.js file is included works fine, but
after that references to the global variable Class references Wicket's
version.
Would it be possible to rename Wicket's Class global to something like
WicketClass
or Wicket.Class?
I only suggest renaming Wicket's version because Wicket isn't trying to
provide a full javascript OO framework.
