Each Activity Space includes the following classes:
Control (optional)
Activity Spaces can include multiple implementations of DisplayPage, Model, View and Control.
The Activity Space class contains the Model-View-Control (MVC) framework and is responsible for initializing the Model, View and Control objects. It also stores data that is globally accessed by the UI.
A DisplayPage class returns the View(s) used for the page. This simple class puts together the HTML and makes it viewable to the user. Each DisplayPage corresponds to an actual portal page; there is a one-to-one mapping between DisplayPages and portal pages.
A Model class defines how data is accessed
and set for a given page, including any functions necessary for security
or data validation and modification.
This class also encapsulates calls to the Plumtree server API and stores
UI-specific data. Control classes use a Model class to perform changes
requested by the user. View classes use a Model class to retrieve data
for display.
Note: Model classes must implement a "Read-Only" Model interface in order to discourage data manipulation in View classes. In most cases, you should add all public accessor methods to this read-only interface.
A View class contains the HTML for the component it represents and describes how the data from the associated Model should be displayed to the user.
A Control class contains an action or set of actions that will be executed when a specific event is triggered. For example, a mouse click could trigger a popup window that displays a View.