Places use History mechanism behind the scenes. It is an abstraction layer which allows you to deal with History from a higher level point of view, and application oriented.
in GWT applications, unlike other traditional web frameworks, we have only one .html page. therefore talking about page1, and page2,is not correct, because there is only one .html page. but to enrich user experience, making your app navigable, bookmarkable, back and forward button to work, you need to manipulate history. instead of dealing with History directly, which is low level, you use Places, as a result you can have different places in your app. HomePlace, AccountsPlace, EmployeePlace, EmployeeListPlace. and this is not just terminology differences. Places are integrated with EventBus, so as you navigate from one place, to another, PlaceChangeEvents get fired. and you can write code to handle these event changes. For example, when you have a list of employees. when you click on (select) an employee on the list, your app can take the user to a new place (employee detail place), to display detailed info on the selected employee. Please have a look at these two very well written articles on Places. GWT 2.1 Places part 1 : http://tbroyer.posterous.com/gwt-21-places GWT 2.1 Places part 2: http://tbroyer.posterous.com/gwt-21-places-part-ii Places are an integral part of GWT MVP framework, related to Activities. if you are not already using GWT MVP, I do not think there would be any benefit in using Places. only adds unnecessary complexity and huge learning curve. I do not know how what you want to do can be achieved elegantly using raw History tokens. Ryan -- 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.
