OOFILE | Downloads | Purchasing | Press | Services | Company Information | Soapbox | References | F.A.Q. | HOME

Installing OOFILE

This section describes how to install OOFILE, and the accompanying ctree Plus package.

OOFILE is usually installed in two separate areas - the OOFILE area and the c-tree Plus area. This separation makes it easy to manage separate updates. Many OOFILE users may already have c-tree Plus installed.

By the way, we'll use the word "project" in this section to describe the base document of integrated environment compilers such as Borland, Symantec or CodeWarrior - you might know this document as an IDE file.

INSTALLING C-TREE

c-tree Plus comes with its own installation instructions that are platform-specific. For Unix and Windows users there are installation scripts that run the process. For the Macintosh, you will have to drag some files together into a folder.

Windows and Unix users will have to build their c-tree libraries, as documented.

Mac users may not need to rebuild the libraries, depending on their environment. For CodeWarrior users, we provide a project to build a library. (Faircom will probably include this on later releases.)

INSTALLING OOFILE

Unpacking the OOFILE archive (or copying from the CD) will give you a small hierarchy of directories:

oofile
- samples

- source
- charts (currently empty)
- core
- ctree
- GUI (will contain various GUI framework subdirs)
- reports (empty unless you've bought reports, or a platform bundle)

Depending on your package, you will see other directories (eg: Unix, CodeWarrior, Symantec_Mac) which contain makefiles and projects for the various compilers.

The Unix directory is always included to give you the Makefile. If you customise Makefiles for your own compilers, please forward a copy and we can maintain it.

If you are running Unix, the makefile in the top directory can make all test programs (make allTests). It will probably require editing to specify the path to the c-tree libraries.

Separately distributed are GUI examples that vary per platform, demonstrating the GUI integration kits. The FileAndFind application will be a common example across platforms, showing basic functions such as:
- database list browsers
- editing dialogs
- edit fields linked to database
- navigation buttons (first/prev/next/last) within dialogs
- embedded tables, for editing child objects.

To make it easier to learn GUI concepts, FileAndFind is repeated in several versions. Each will add more functionality, or show alternatives for the platform. (eg: on the Mac, using the proprietary StoneTable list control vs using PowerPlant native table classes.)


 

Feature index

(c) Copyright A.D. Software 1994-2000 (All Rights Reserved).
Last Updated: 9th September 2001