|
|
How to use the OOF_Debug and OOF_SmartHeap #defines to ensure the safety of your database.
A list of a couple of minor problems that you can run into and the error messages likely to be seen. Running in OOF_Debug mode should help avoid or diagnose most mistakes you can make.
Just the limits on numbers of classes, indices etc.
Describes the general dependency mechanism in OOFILE which you can use for your own dependencies, as well as its use by dbTable and other classes.
A kind of grab-bag of our programming conventions, c++ concepts and a resource list for c++ programming, object-oriented design and other topics.
How the c-tree multi-user capabilities are used in OOFILE.
A few minor issues in going cross-platform. Read this document to see how to get the most efficient space packing of your objects and to be sure that your database can be copied to other platforms.
A couple of minor c-tree source code changes are required for Mac programmers writing GUI applications, with c-tree prior to 6.7 (around 1997 vintage). Also describes how OOFILE makes use of c-tree features.
Some interesting questions from user correspondence.
The test plan followed in validating an OOFILE release.
Describes some OOFILE internals in terms of the GOF Patterns,
and our own efforts.
(See "Design Patterns" by Gamma, Helm, Johnson & Vlissides)
The different components of OOFILE.
Major database classes and backends.
Including some portions linked to a rough reference manual.
How OOFILE links your database to an application framework.
Describes some OOFILE internals in terms of the GOF Patterns,
and our own efforts.
(See "Design Patterns" by Gamma, Helm, Johnson & Vlissides)
Summary of the main features OOFILE adds to enhance c-tree Plus.
Comparison to the ODMG-93 Standard
Describes OOFILE features side by side with ODMG definitions and discusses some future compatability improvements.
The Diary-Driven approach we use to manage development.
Using the AppMaker code generator program on Macintosh and how OOFILE applications can be automatically generated for the PowerPlant framework.
The common philosophy to integrating OOFILE into application frameworks
Use Cases (from Jacobson) describe sequences of actions in a typical GUI database application.
The points at which you can easily customise gui integration behaviour by overriding virtual methods.
The (Macintosh) MetroWerks PowerPlant GUI integration, and the basis for our future GUI integrations.
A short reference to the basic commands for dealing with the database.
A short form of this index for quick referencing.
Ever-improving, the automatically generated reference of all classes and methods in OOFILE.
(c) Copyright A.D. Software 1994-2002 (All Rights Reserved).
Last Updated:12 January 2002