The Text Objects: 3 The Text Object Library

Up: GEOS SDK TechDocs | Up | Down | Prev: 2 General Text Features | Next: 4 Text Object Chunks

Both Text Objects rely on a single framework; this framework is the Text Object Library. The Text Object Library ( tCommon.h ) contains many definitions and structures that text objects will use. Every definition and structure in this section can be used by both VisText and GenText objects.

VisTextClass is the class that utilizes most of these features directly. GenTextClass also utilizes almost every one of these features through VisTextClass . This is because GenTextClass , as a generic object, is manifested through VisClass by specific UI libraries.

The text library also has data structures and mechanisms defined to support other features that, due to time constraints, have no strict API definition in the library. To provide these "potential features" in your applications, you can directly access the text data structures and set them appropriately. (For example, automatic paragraph numbering is not directly supported, but the paragraph attributes data structures allow defining characters that get prepended to individual paragraphs.)

Many of the features are implemented and controlled automatically by GEOS. For common features (character styles and font sizes, for example), controller objects can handle almost everything. For less common features (automatic paragraph numbering, for example), your application will likely have to provide the UI and the control mechanisms necessary.


Up: GEOS SDK TechDocs | Up | Down | Prev: 2 General Text Features | Next: 4 Text Object Chunks