Am Freitag, 8. Juli 2011 12:57:01 UTC+2 schrieb Eugen Paraschiv:
>
> Perhaps the solution is to consider abc:null as a place where no element is
> selected and then let the user select the element.
>
Thats what I do when a user visits a place the first time after a fresh app
start. Once the user selects something I go to the new place that reflects
the selection. In addition I update the menu item link that leads to that
place. That way the user can navigate away..but when he comes back to that
place he sees the last selection he has done. So basically I only do
placeController.goTo(..) when the state changes inside a place. All other
navigation is done directly with Hyperlink instances with the history token
as url (so all my navigation widgets listen to PlaceChangeEvent and update
the corresponding hyperlink).
For example I have a side menu which contains new Hyperlink("#employees").
Once an employee is selected in the list the side menu item url gets updated
to "#/employees/<selected id>". Thus the selection is saved inside the
hyperlink itself.
That was a nice solution for me and maybe for you too. Just imagine if you
select an item automatically, it may occur the case that the user is not
interested to see that automatically selected item and then you have also
done some additional http requests just to load "the one the user is not
interested in".
-- J.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/Q1uRZLsPglgJ.
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.
