The programming model implemented by Bean Works is based on a model-view-controller (MVC) paradigm. This design allows you to partition your component's data (the model) from the display or interpretation of that data (the view), and bind them together at runtime (via the controller) along with other variable aspects of your component such as a localized interface.
This approach provides several benefits, giving you the ability to, for example:
The framework extends the model-view-controller paradigm by adding support for end-user features, including basic document commands such as New, Open, Save, and Save As. The framework also support limitless undo and redo of commands, cut, copy and paste, and other default behaviors.
The following sections describe the key aspects of the Bean Works programming model. See Bean Works Architecture for information on the specific Java classes that implement these concepts.
Model-View-Controller Component Design
The model, view, and controller represent the key portions of a Bean Works component, defining how data is stored and rendered and how it is presented to the user. The component controller controls the entire component--it delegates events to the model and view, and provides access to their properties.
Selecting and Manipulating Data
Bean Works provides mechanisms for selecting data in a model and for issuing commands against selected data, allowing you to clearly partition data storage and management from the mechanisms provided for a user to manipulate the data.
Bean Works includes a command processor that maintains a log of commands as they are executed, allowing unlimited serial undo and redo of commands in the chain.
Copyright ©
Taligent, Inc. 1996 - 1997.
Copyright © IBM Corporation 1996 - 1997.
All Rights Reserved.