If you are making use of Places, you'll define an Activity for\n each of them; all activities are derived from com.google.gwt.app.place.Activity. If you\n have common functionality that you wish to use for your Activity classes, implement\n it in a class derived from com.google.gwt.app.place.Activity and specify that class\n in the useBaseClass attribute of your defined Activity.\n
\n Activities are meant to be short-lived, disposable entities that run in a particular Place.\n However, if you are building an application, it may be that you have a single Place and\n that all behaviour takes place within the guise of a single Activity.\n
\n If the Activity manages a view, it will be generated as implementing the View's \n presenter interface.\n
\n Activities provide a natural division point for GWT code splitting, if you've structured your\n code appropriately. By specifying the codeSplit flag as true, the code for the Activity will be \n asynchronously loaded using the GWT code splitting mechanisms.
Generated from the mvw schema at version 0.1
This code was auto-generated by the dmogenerator utility and shouldn't be alterred manually! Generated from: org.dmd.dms.util.DmoFormatter.dumpDMO(DmoFormatter.java:133)