On 27 mai, 13:41, Tristan <[email protected]> wrote: > I've written a wiki on how Place Service is implemented in Handlebars. > However, after the fact I realized that it's also a HOWTO document of > a way to implement a place service in general that is fairly robust. > > I hope you'll find this document useful, and I'd be happy to answer > any questions or hear your comments. > > http://code.google.com/p/handlebars/wiki/PlaceServiceOverview > > Cheers!
Have you measured using a GWT event per place vs. a single GWT event carrying a Place object? (BTW it would cut the number of classes by 4 --no need for both a AtLandingPage and GoToLandingPage events, and their corresponding EventHandler interfaces, just a LandingPage place) I also notice that: - the GoToPlace is only used to talk to the place service, how about having the place service injected and call a goTo() method on it directly? - the GoToPlace "request" is imperative, it cannot be cancelled (e.g. you changed some field values and you want to ask the user confirmation before leaving without saving his changes); this would be fixed if it wasn't an event fired by the class that "triggers" it but by the PlaceService itself. - you're forcing everyone to use your #sometoken? some=query&string=like&name=value&pair=parameters kind of history tokens, what if I'd prefer something like #/documents/some/folder for instance? Have you seen the work being done in GWT itself in the bikeshed project? (look into the branches/2.1 branch in SVN, not the trunk) It does not yet link places to the browser history but allows previewing (and cancelling) the GoToPlace event (or equivalent). My own PlaceManager (at work, not open source) does the same too. -- 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.
