History, History tokens, links and ValueChangeHandler work hand in hand to
provide psuedo navigation within the client code. The Google GWT docs cover
all these in detail and offer numerous code samples too.

In short, add a history token can procedurally be added to History causing
the url in the browser to change to reflect the token in the form of
#valueoftoken. In conjunction with this, your value change handler is
notified of the history changed state passing the token in a
ValueChangeEvent object. Your code can then process the event notifications
and act accordingly. Links are a declarative way of changing the history
state and also cause value change events to be fired so you can use either
of these patterns in your application.

Jeff

On Fri, Nov 26, 2010 at 9:00 AM, Magnus <[email protected]>wrote:

> The commands should open some panels, so they are on the client.
>
> I want to present a list of items, and one click on one item should
> open the details.
>
> Can you please describe your method with the History tokens?
>
> Thanks
> Magnus
>
> --
> 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]<google-web-toolkit%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>


-- 
*Jeff Schwartz*

-- 
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.

Reply via email to