Adding a form

Creating a brand new form / service / report that has never existed before is a special case in a Configuration Managed environment. When Uniface is using the UD6/CMTOOL driver it will always assume that if a ‘file’ does not exist in the ‘reference area’, then it does not exist.

This also applies to a new table / sub-type / library etc, but not a new register, field etc since these exist ‘within’ an existing entity.

So the easiest way to create a new form, is to copy an existing form file, remove its contents apart from the header and footer, check it in to CVS and then check it out and use it as normal.

e.g.:

New.xml contains:

<?xml version="1.0"?>

<uniface_schema >

</uniface_schema>

To put this source into the repository run this CVS command:

md new

md components

copy \new.xml .

cd ..

cvs import -m "Initial import" .  Trunk unifaceapp_1_0

NOTE: The import command in CVS always imports an entire tree, so be sure to create the tree empty.

The form can then be checked out and worked on as described previously

What is CVS
How to get and install CVS
Configuration information
Taking control
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.11 $ $Date: 2011/02/28 02:56:33 $[go to top]