title: How do I keep smartgwt from polluting the window namespace?
body: <p>I have existing javascript in a project that creates a 'Calendar' object. The object is a member of <code>window</code>.</p>
  
  <p>When I added smartgwt to my project, the original Calendar object was overwritten by a smartclient calendar (ISC_Calendar) packaged in smartgwt.</p>
  
  <p>Using a browser-based JS debugger, I found that all the JS objects from smartgwt were contained both in <code>window</code> and in <code>window.isc</code>. I definitely don't want them all at window level because many of them have generic names like Calendar.</p>
  
  <p>The offending file in my case is ISC_Calendar.js, which ends up in war/&lt;projectname&gt;/sc/modules after a gwt compile. It calls the following line: <code>isc.ClassFactory.defineClass("Calendar","Canvas","DataBoundComponent");</code></p>
  
  <p>GWT compiled location: war/projectname/sc/modules/ISC_Calendar.js<br>
  Jar location: com.smartclient public/sc/modules/ISC_Calendar.js<br>
  Src location: can't find it</p>
  
  <p>I suppose I can just change the javascript file in the jar I'm using, but that doesn't really solve the larger problem. I don't want to worry about running into namespace issues down the road</p>