Hi, you can use "deferred binding" to compile different instances for your webapp. "Help facility" behaves like an other browser or locale More on http://code.google.com/intl/de-DE/webtoolkit/doc/latest/DevGuideCodingBasicsDeferred.html
Stefan Bachert http://gwtworld.de On 21 Apr., 14:32, "[email protected]" <[email protected]> wrote: > Hi all, > > After a little guidance on this topic - not quite sure what approach > should/would work. In the GWT app I'm developing, I'd like both the > server/client side to have a "demo mode" that enables certain help > features and enforce certain beginner workflows. > > I know I can get the parameters of the URL using GWT, but the user can > simply remove the demo parameter to disable it (www.../index.html? > demo=1), so I'm after some way to enforce this at the application > level. At the same time, I don't want to be having a boolean flag in > the code/HTML and recompiling/deploying it each time. > > Whats the best way to implement something like this so that the enable/ > disable switch can be easily configured without recompiling/deploying? > (Can an argument be passed to the server side by the application > server when it starts? Can there be a config file outside of the WAR > file?) > > thanks > Sunny > > -- > 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 > athttp://groups.google.com/group/google-web-toolkit?hl=en. -- 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.
