I have run into the same issue. It is true the tokenizer is not added to the
mapper, than it works, only that means that I'm forced to go with a all or
nothing approach. What I would be interested in is to be able to
programatically decide when to trigger a history item addition and when not
If you don't add MyPlace.Tokenizer.class to your AppPlaceHistoryMapper the
activity will be fired but the history won't change
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to
I may be way off the track here but I have a Place Activity for
searching items. When an item is clicked, the Place and Activity are
changed to such that allow the editing of an item. What I would like
is that the token of the edit place for editing is not added to the
history and the current URL
If the history token doesn't change, then you haven't navigated to another
place; i.e. IMO you should do it all in the same place and activity (use
case looks weird though at first sight :-/ ).
Your edit screen can however very be re-used by an activity corresponding
to the edit place used
Hi Thomas and thanks for the insight,
Creating a new item consists of searching for some initial, immutable
properties for this item AND editing some mutable properties for it.
Then later, these mutable properties can be changed.
So yeah I guess searching and editing should happen in one place
