The Showcase is a pretty neat example of how do you go about handling skins: * Go to http://gwt.google.com/samples/Showcase/Showcase.html * Click in one if the colored rectangles located in the top right corner of the page * Voilà ! (Profit ? :) )
You can look at the code that handles that in the samples included in the GWT distribution and then adapt it to suit your needs Cheers, Salvador On Apr 15, 2:29 am, matttai <[email protected]> wrote: > Yep you are following my train of thought exactly. > > I'm thinking in terms of using deferred binding for skin/layout > differences it shouldn't be such a bad idea if it's small alterations > such as colours/layout. > Considering that internationalisation/browser layout differences work > along the same lines in terms of the scope of changes. > > The workflow i've had it laid out in though in my head is like this: > > 1. default entry point with default permutation is loaded with login > form > 2. user logs in with user / pass / layout > 3. system checks for valid login > 4. if successful login redirect back to default entry point with > <when-property-is name="skin" value="GREEN_LAYOUT"/> > > My issue is on the redirect how would i go about setting the property > value that i wish to load? > Would this be appended to the URL ala locales in > internationalisation? > > This then brings up another issue. If it does involve appending to the > URL what if i only wish to make the skin available to only a > particular set of users. > > Else i'm thinking at this point maybe dynamically downloading and > loading skin X after login may be a better choice as opposed to > deffered binding. > > On Apr 15, 12:23 am, gscholt <[email protected]> wrote: > > > On Apr 14, 9:09 am, matttai <[email protected]> wrote: > > > > Hi everyone, > > > > Been checking out alot of thedeferredbinding tutorials that seem to > > > involve reading from the meta data in the html before loading the > > > appropiate module. > > > > If i wanted to load adeferredbinding 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. > > > "Deferredbinding 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#D... > > > If you usedeferredbinding 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
