Components

A component is a self-contained functional unit roughly equivalent to an application plus data. A component contains native data and possibly one or more other components. Components can be created explicitly using stationery pads or implicitly during paste or drag-and-drop operations.

Components allow functionality to be broken down into smaller, composable pieces. Smaller pieces of functionality make it easier for users to integrate new data types into documents. Different types of data presented in a single document are live--the user can edit each data type in place without switching documents. The user brings the necessary tools to the data without having to change the current context. Users can create exactly the documents they want without requiring a single application to provide all the functionality they need. Components thereby free users to focus on the task contents, not on how to perform the task.

Components also offer a context for scoping commands related to finding and organizing, and communicating and collaborating. Users can search for data within and across components using content-based retrieval methods.

Developers will benefit from components because they support code reuse. Reuse helps free developers to focus on the functionality they want to provide, while lowering their development costs and increasing the opportunity for greater deployment due to the portable nature of the CommonPoint environment.


[Contents] [Previous] [Next]
Click the icon to mail questions or corrections about this material to Taligent personnel.
Copyright©1995 Taligent,Inc. All rights reserved.

Generated with WebMaker