On 21 juil, 01:54, PhilBeaudoin <[email protected]> wrote: > Another approach that wasn't mentioned but that I use quite frequently > is to use the history and pass the information as parameters in the > history token. This is made really easy in frameworks like gwt- > presenter and gwt-platform and has a number of advantages provided the > parameter is serializable (and small enough). For example, it could > let the user bookmark the detail page of "Lady_Gaga". A bit trickier > when the presenter is a dialog box, but totally doable.
This has the drawback that you cannot "cancel navigation" (because in this case it's about navigation, not "any custom event"), e.g. for cases where you changed some values in a form but didn't save them. But this is easily solved by frameworks with the concept of "places", that generally have 2 events: place change requested (cancellable) and place change (in case the first wasn't cancelled). It just moves the problem though, it doesn't really solve it (what if you didn't "serialize" 'enough' information into the "place"?) -- 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.
