If you've started using GWT 2.1 Places and Activities with the Milestone 3, then here's what changed in the Release Candidate 1. I'll update my previous articles in the coming days to reflect those changes.
com.google.gwt.app.placepackage has been split into the
com.google.gwt.user.client.ui.AcceptsOneWidget, which is implemented by
showActivityWidgetis thus renamed as
IsWidgethas been moved to com.google.gwt.user.client.ui and is now implemented by
Widget(which returns itself); this means that if your view classes
extends Widget(most views extend it through
Composite) you no longer have to implement the
- In addition, all widgets now accept
IsWidgetas argument where they already accepted
@Deprecatedand no longer implements
EventBus; you'll now use a
SimpleEventBusfor your application-wide event bus.
PlaceHistoryHandlerhas been split into a concrete
PlaceHistoryMapperinterface, which you're free to implement yourself or use as before, giving your sub-interface to
GWT.create()so that it generates the implementation from the
@WithTokenizersannotation (and/or factory if you're using
PlaceHistoryMapperWithFactory); this approach is similar to the
ActivityMapper, with the added generator for the mapper based on
ProxyListPlaceand associated classes (and abstract activities) have been moved to the Expenses sample (which doesn't use them yet).
And this list is only about the Places and Activities part:
RequestFactory's API has been deeply refactored, and a new
Editor module is born!