OOFILE  1.9
Modules
Here is a list of all modules:
[detail level 1234]
 Application AuthoringClasses to assist in writing applications
 OOFILE utility classes and functions.Included in the Open Source OOFILE
 OOFILE macrosCollection of all important macro definitions regardless of package
 Database DeclarationsUsed to make it simpler to write persistent table declarations by including common methods and defining relationship field types
 Compiler features we expect or useMany of these can be set, especially with Unix compilers, to tell OOFILE what features are available
 Exception Handling enabling as optionException handling is optional in OOFILE and you can build without exceptions defined
 Platform specifiers.As discussed on Platform Definitions and defined in oofplat.h
 Report Writer feature availablitySome features are optional to avoid having to link in XML processing or control what toolbars are used for report previews
 Reliance on C++ Standard Library FeaturesAffect how OOFILE is built with regards to the standard libraries, which can be important on legacy systems or if using parts of OOFILE like oofString in component code
 Version Numbers for the different packages.Use \ingroup oofVersionMacros to include items in this group
 MFC application framework Only.Use \ingroup oofMFCMacros to include items in this group
 PowerPlant application framework Only.Use \ingroup oofPPMacros to include items in this group
 DLL Export MacrosOOF..._EXPORT macros are used to export/import classes or functions to/from DLL
if DLL is created, the OOF..._CREATE_DLL must be set on
if DLL is used, the OOF..._USE_DLL must be set on
if DLL is not used (so static library OOF...LIB.LIB is linked or created) both macros
(OOF..._CREATE_DLL and OOF..._USE_DLL) must be set off; OOF..._EXPORT will be expanded to an empty string
on non-Windows platforms, the OOF..._EXPORT macros will be expanded to an empty string
 OOFILE XML support.Includes tools for reading and writing XML in general and generating XML Schema descriptions and reading and writing OOFILE databases as XML
 OOFILE exception hierarchy to provide structuredError reporting
 OOFILE file and directory manipulation.Cross-platform classes for iterating directory trees, copying and managing files, reading and writing text files
 OOFILE Database package
 Local variables compatible with database fields.
 OOFILE Database backend for Faircom's ctree-Plus ISAM engine.The main component of the commercial OOFILE Professional version
 OOFILE Database backend for dBase III+ and IV-compatible data.The main component of the commercial OOFILE Personal version
 OOFILE Database backend for Faircom Server.The main component of the commercial OOFILE Professional Server Edition, which includes OOFILE Professional and adds support for the Faircom client-server version of c-tree Plus
 OOFILE Database QueryClasses that allow you to build queries either:
 OOFILE Database backend for simple streamable RAM databases.Included in the Open Source OOFILE
 OOFILE Database backend for persistent RAM-resident databases.Use \ingroup oofDatabase_ramp to include items in this group
 OOFILE GUI forms interface.
 Presentation for OOFILE Databases
 OOFILE Graphing engine.Graphing engine for Mac and Windows, usually used within reports
 OOFILE Report writer
 Multiple platform renderingGroup rendering classes for each platform
 Macintosh Report renderingReports rendered to the Macintosh GUI drawing environment able to be previewed and printed under Classic MacOS and MacOS/X using Carbon
 CSV Report rendering.Reports rendered to Comma Separated Value text streams
 HTML Report rendering.Reports rendered to HTML text streams
 RTF Report rendering.Reports rendered to Rich Text Format text streams suitable for import into MS Word or other word processors
 Tabbed text Report rendering.Reports rendered to tab-separated text streams suitable for import into spreadsheets or other databases
 Plain Text Report rendering.Reports rendered to text streams in simple fashion
 MS Windows Report renderingReports rendered to the Win32 GUI drawing environment able to be previewed and printed under MS Windows
 XML Report rendering.Reports rendered to XML including layout, data schema and all source data suitable for re-opening with any OOFILE reporting application and editing in the report preview window
 Interfaces possibly implemented by report objects.This pattern is used to avoid use of RTTI within the OOFILE despatching, but still be able to use mixin approaches to add interfaces and members to some classes - which traditionally requires downcasting with dynamic_cast
 Report Editing supportReport preview windows allow editing with a user-overrideable editor, usually a dialog that can step through cells of the report
 OOFILE Report writer Professional Version
 Report Reading From FileProvide the ability to read a report from a single XML document
 OOFILE Character-mode simple report writer.Simple reports that output just one table formatted as plain text with spaces and returns or simple HTML
 OOFILE Implementation ClassesSeparately grouped so you can quickly see what are private classes
 Experimental code, may change considerably.Used to mark code during development and which sometimes has to be left in release versions, but which may change interfaces or implementation
 Mac SpecificUser code will often wrap in #ifdef _Macintosh Only ever used on Macintosh
 PowerPlant application framework Only.Use \ingroup oofPPMacros to include items in this group
 MS Windows SpecificUser code will often wrap in #ifdef _Windows Only ever used on MS Windows
 MFC application framework Only.Use \ingroup oofMFCMacros to include items in this group
 DLL Export MacrosOOF..._EXPORT macros are used to export/import classes or functions to/from DLL
if DLL is created, the OOF..._CREATE_DLL must be set on
if DLL is used, the OOF..._USE_DLL must be set on
if DLL is not used (so static library OOF...LIB.LIB is linked or created) both macros
(OOF..._CREATE_DLL and OOF..._USE_DLL) must be set off; OOF..._EXPORT will be expanded to an empty string
on non-Windows platforms, the OOF..._EXPORT macros will be expanded to an empty string
 Unix SpecificUser code will often wrap in #ifdef _Unix Only ever used on Unix