Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep
Home >> All >> org >> scopemvc >> [ core Javadoc ]

• org.scopemvc.core: Javadoc index of package org.scopemvc.core.


Package Samples:

• org.scopemvc.core

Classes:

• Controller: Controllers arranged in a hierarchy of chains of command provide the structure of an application's logic, mirroring independent contexts of discrete View s and their bound model objects. Each context can be treated as an independent component. Application logic invoked by sending Control s into the chain executes in the context of a Controller that specifically recognises and responds to the Control by its ID. For example, a Controller might manage a search panel (eg CustomerSearchView and bound CustomerSearchModel) that can be embedded within other arbitrary views. The search panel context has ...
• Control: A token passed up the chain of Controllers to invoke a piece of presentation logic. Controllers match against the ID of a Control passed into handleControl 55 If the ID is recognised then the Controller can execute some presentation logic. If the Control ID is not recognised, the Control should be sent back on its journey up the chain of responsibility by passing it to the parent Controller. See org.scopemvc.controller.basic.BasicController#passControlToParent . Controls are received by a Controller from either a View or a child Controller. Controls can optionally contain an Object parameter: see ...
• ModelChangeEventSource: Implemented by model objects that fire ModelChangeEvent s when their state changes: an implementation of the Observer Pattern. The Swing components in org.scopemvc.view.swing are aware to ModelChangeEvents: model objects that implement this interface are able to automatically refresh any View s bound to them. If a submodel of a model changes, the parent must also fire a ModelChangeEvent to notify of the change in state of one of its properties. For example, if a Person has a Pet as a property, then when the Pet changes its age it fires an event to notify of a change to the "age" property. The Person ...
• ModelChangeListener: Implemented by objects that can receive notification when a model object implementing ModelChangeEventSource changes state. To use: Implement this interface, responding to the change in Model state in modelChanged(org.scopemvc.core.ModelChangeEvent) 55 , Register as a listener to a Model using ModelChangeEventSource.addModelChangeListener(org.scopemvc.core.ModelChangeListener) 55 , Deregister as a listener when no longer interested in receiving notification of changes using ModelChangeEventSource.removeModelChangeListener(org.scopemvc.core.ModelChangeListener) 55 .
• View: A View implements the presentation of a model object to the user and allows interaction with the model object. Implementations can be bound to a model and change the state of the model as the user interacts with the View. If the View implements ModelChangeListener then it can also update in response to changes in the state of bound models that implement ModelChangeEventSource. A View can also issue Controls to its parent Controller in response to user interaction that influences with application logic. A View is bound to a single model object, i.e. it presents some or all of the data in the bound ...
• Selector: An identifier for model properties. Selectors are created by the factory methods fromString(java.lang.String) 55 and fromInt(int) 55 . Properties can be identified by a String name (eg the "address" property of a Customer) or an integer index (eg element 1 of a List). Selectors can be assembled in a list to identify a property in a model contained within another model. For example, the name of the pet of a Person . This Selector would be created by Selector.fromString("pet.name") and applied to a Person model object. Similarly, the name of a Person's first pet could be identified using Selector.fromString("pets.0.name") ...
• ModelChangeEvent: Event that is broadcast to notify interested ModelChangeListener s of a change in state of a model object implementing ModelChangeEventSource . It contains: the source of the event (ie the model object that changed), the Selector identifying the property that changed, and a 'type' of change (see ModelChangeTypes ). Note that the event does not contain the actual data that changed, unlike JavaBeans PropertyChangeEvent.
• ControlException: Controller s throw ControlExceptions while responding to Control s if something goes wrong that must be reported to the user. A ControlException is a org.scopemvc.util.LocalizedException . ControlExceptions contain a Control ID that can be used by an error handler to identify the Control that caused the exception. For example, the Control ID could be used to get a String title from UIStrings for a Swing error dialog. The error handling implementation in BasicController automatically populates the Control ID.
• ModelManager: ModelManagers provide decoupled operations on model objects including access to properties and invocation of actions. A manager instance for a specific model object is obtained by a static factory method in the manager subclass. Other managers can be plugged in as appropriate to provide different functionality required on model objects. The base Scope implementation provides PropertyManager , ActionManager and EditorManager implementations.
• EditorManager: EditorManager is a ModelManager that handles the creation of appropriate Viewer and Editor Views for the properties of model objects for a specific view type. An implementation for JavaBean model objects is provided in org.scopemvc.model.beans.BeansEditorManager . The viewtype passed into this manager is arbitrary and identifies the particular type of View an application is interested in. For example, "swing" or "xml" or "awt". See org.scopemvc.view.util.PropertyEditorFactory .
• IntIndexSelector: An implementation of Selector that identifies a property by its int index within the parent model object. This is used to access properties in java.util.List and Object[]. Create by Selector.fromInt(int) 55 or Selector.fromString(String) 55 .
• ModelAction: Actions on model objects can be invoked via ActionManager 's API, taking a ModelAction to describe the method to invoke. A ModelAction contains a method name and a Class[] to describe the parameters in the method signature. ModelActions are probably not used by application builders who will more likely call a model object's methods directly.
• ActionManager: ActionManager is a ModelManager that handles the actions (invokable methods) of model objects. The core of Scope doesn't depend on this manager although this abstract class is in the core package for consistency with the PropertyManager. An implementation for JavaBean model objects is provided in BeansActionManager.
• StringIndexSelector: An implementation of Selector that identifies a property by its String index within the parent model object. Create by Selector.fromString(String) 55 .
• PropertyManager: PropertyManager is a ModelManager that provides access to the properties of model objects. An implementation for JavaBean model objects is provided in org.scopemvc.model.beans.BeansPropertyManager.
• PropertyView: A View that can be bound to a property by specifying a Selector . Most view implementations will implement this interface.
• ModelChangeTypes: Constants for types of model change used in ModelChangeEvent .

Home | Contact Us | Privacy Policy | Terms of Service