See: Description
| Interface | Description |
|---|---|
| App<M extends AppModel,L extends AppLogic,G extends AppGui> | |
| AppComponent<A extends App> | |
| AppGui<A extends App> | |
| AppLogic<A extends App> | |
| AppModel<A extends App> |
| Class | Description |
|---|---|
| AbstractApp<M extends AppModel,L extends AppLogic,G extends AppGui> | |
| AbstractAppComponent<A extends App> | |
| AbstractAppGui<A extends App> | |
| AbstractAppLogic<A extends App> | |
| AbstractAppModel<A extends App> |
Partner applications, such as the Map Viewer (MapApp) and Workbench (WorkbenchApp) have evolved to a standard, hierarchical organizational structure. There is a top-level "app" object, which then generally has three major subobjects - a model, a gui, and a logic. This is very similar to the Model-View-Controller (MVC) architecture used in most modern application frameworks.
The model, represented by the AppModel interface, is the domain model for the application.
The view or gui, represented by the AppGui interface, is the view model for the application. It's not merely a passive view, but has it's own controllers and plumbing. However it is intended to be fairly "stupid", functioning only as a facade to the underlying business logic and model.
The logic, or controller, represented by the AppLogic interface, is the controller and business logic for the application.
Copyright 2011 Partner Software, Inc.