On Apr 14, 9:09 am, matttai <matt...@hotmail.com> wrote: > Hi everyone, > > Been checking out alot of the deferred binding tutorials that seem to > involve reading from the meta data in the html before loading the > appropiate module. > > If i wanted to load a deferred binding class after a user logs in (eg. > after the user logs in load the same app with a different skin and > interface) > > Would this involve something like using JSNI to change the meta in the > html after a user logs in and forcing a refresh? > > Or is there a better approach to doing this.
"Deferred binding is a feature of the GWT compiler that works by generating many versions of code at compile time, only one of which needs to be loaded by a particular client during bootstrapping at runtime." -- http://code.google.com/webtoolkit/doc/1.6/DevGuideCodingBasics.html#DevGuideDeferredBinding If you use deferred binding for skin support (which might not be a bad idea, depending on the amount of skins and the amount of code they generate), you will need to reload the application to get a different compiler permutation. This includes reloading the HTML, since you'll need to run the GWT bootstrapping code again, which selects the correct permutation depending on the set properties, using something like <property-provider name="skin">...</ Gert --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
