Final directory structure

Now that all of this setup has been done, you should be able to check in and out your Uniface source code, search it with any standard tool, and use it from within the IDF. The final directory tree looks like:

p:\Nettest
\s
\applications
\components
\globals
\glyphs
\menus
\other
\registers
\subsystems
\sub-types
\tables
\templates
\type-libraries
\Sources
\applications
\components
\Cvs
\globals
\glyphs
\menus
\other
\registers
\subsystems
\sub-types
\tables
\templates
\type-libraries
\Cvsroot
\Controlled_Sources
\applications
\components
\Cvsroot
\globals
\glyphs
\menus
\other
\registers
\subsystems
\sub-types
\tables
\templates
\type-libraries

Then the ‘additional’ directory tree ‘p:\nettest\s’ can be removed.

Taking Control

Taking control
Directory structure
Import to the CM Tool
Creating a Reference Copy
Keeping the Reference Copy up to date
Final Directory Structure

How to use the driver with a configuration management solution (cont.)

Releasing a form
Checking a form in
Releasing a form and application model
Releasing registers
Adding a form
Differences
Merging code changes
Final notes

UD6 Overview
A methodology to Uniface source code control

$Revision: 1.13 $ $Date: 2011/02/28 02:56:33 $[go to top]