On Feb 13, 3:06 pm, Tuvok <[email protected]> wrote:
> Hi guys,
> I'm elaboratating the strategy to take in the devolping of my first
> gwt app; it's gonna be an online tournament and matchmaking system
> supporting team managing and other (in my mind :D) cool features.
> I am using Tomcat/Apache as Web Server and RPC target and EXT GWT on
> the client side.
> At first I thought about using a single host page and manage
> everything through panels/widgets adding-removing-modifying, but I
> ended up thinking that in this case users wouldn't be able to exchange
> urls pointing to a specific page (ie, if I wanna tell you, 'go check
> out my team athttp://site.com/viewteam.html?teamID=10'I can't
> because there's a single page, index.html).
> So I thought about splitting every page, but then, how can I make GWT
> catch the data stored on the parameters?
> IE on home page I have a link to viewteam.html?teamID=10, GWT catches
> the teamID parameter, calls a RPC to the server using that ID and
> populates the widgets, is this the correct way to go? If so, how to
> make GWT catch that data?
GWT History tokens are passed in the fragment part of an url, if you
link to http://site.com/viewteam.html#teamId=10, you can use
History.getToken() to return you the String "teamId=10". Or better
yet, register an handler and run History.fireCurrentHistoryState().
See the documentation on the history stack and using it for program
state.
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
-~----------~----~----~----~------~----~------~--~---
