IMHO, pollution of the global namespace is a big problem for general purpose apps. It's ok to do it when you control everything (e.g. Wave), but probably a bad idea for enterprise users who have a habit of composing lots of small GWT modules on a single dashboard. We probably need to support both explicit scope and polluting options, and allow the developer to choose.
-Ray On Tue, Nov 24, 2009 at 8:33 PM, Scott Blum <sco...@google.com> wrote: > On Tue, Nov 24, 2009 at 9:39 PM, Matt Mastracci <matt...@mastracci.com>wrote: > >> Hey Scott, >> >> I've ported hosted.html over to hosted.js a few times and it's not >> actually a problem. The only significant differences between the two files >> are s/parent/window/ and how you pass the name of the module to the >> hosted-mode bootstrap script. Each version of the plugin tested (Safari, FF >> and IE from a few months ago and recent Safari/FF builds) has been able to >> work in this environment without modification. >> >> I don't think the hosted-mode plugin would work with the privately-scoped >> XSLinker today, but it definitely works with our modified version that links >> the JS at the global scope. >> > > Okay, that makes sense to me. I think to really ship this, though, we want > the plugins to put their symbols into a private namespace. Otherwise two > modules on one page would step all over each other, for example. > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors