On Thursday, May 17, 2012 4:42:13 PM UTC+2, Shaun Tarves wrote: > > It's about optimization, I guess. If you just have a shallow Place object > (say it only knows an ID) and always fetch the data you need, that means > more calls. > > If you let the Place object contain a lot more data, you still have to > code for when it doesn't (eg., when the user navigates directly to a URL or > does a right-click -> Open in new tab...). > > I was just curious if there's a preferred pattern here. >
IMO you should prefer the preventDefault+PlaceController#goTo way (and don't forget to code the "fallback" in the target PlaceChangeEvent.Handler and/or Activities!), as it's really small overhead for the developer (you could even make a PlaceHyperlink(PlaceHistoryMapper, Place) to avoid repeating the same things again and again) and a real win for the user. -- 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/-/a-fAcWjwkGYJ. 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.
