On 14 avr, 09:09, matttai <[email protected]> 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.
Decouple your login "app" (page) and your GWT application? (depends
how you manage authentication though)
As for your other "problem": if I were you, I'd compile the "skins" as
distinct "apps", each with its own HTML host page; this would allow
you to setup a filter to deny access to some "skins" depending on the
logged-in user (again, depends on how you manage authentication).
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
