Adding a form using PVCS Version Manager
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 (file).
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 PVCS Version Manager and then check it out and use it as normal.
<?xml version="1.0"?> <?xml-stylesheet href="components.xsl" type="text/xsl"?> <?xml-stylesheet href="components.css" type="text/css"?> <uniface_schema xmlns:html="http://www.w3.org/TR/REC-html40"> </uniface_schema>
To put this source into the PVCS Version Manager project database you need to log into PVCS Version Manager as whoever has access to check in and create a new workfile.
From the main screen open up the My Project Databases tree, then the project database that you have loaded the workfiles into (our example uses BrdalDatabase). When you find the components directory.
Select File ->Add Workfiles from the pulldown menu, and then select the file new.xml.
You may be prompted for a Check In description, enter this, and ensure that Delete file after check in is set ON, then accept it by pressing OK.
The form can now be checked out and worked on as described previously.
NOTE: Even though there is an XML file, since it is empty of any data, the IDF will not show that the ‘FORM’ exists. Once the XML file is checked out, you can create the ‘FORM’ in the usual manner in the IDF.
How to use the driver with PVCS Version Manager (cont.)
Taking control in PVCS Version Manager
Releasing a form using PVCS Version Manager
Checking a form in using PVCS Version Manager
Finding the differences in versions using PVCS Version Manager
Procedures for handling compiled objects with Version Manager
Problems when using PVCS Version Manager
A methodology to Uniface source code control
|$Revision: 220.127.116.11 $ $Date: 2003/09/16 17:51:59 $||[zum Seitenanfang]|