Design Versioning

Source Control Configuration

PADS I/O Designer supports several source control systems, such as:

To choose a source control system, open the Setup > Settings dialog. On the Source Control page a system may be chosen. Additional configuration settings are available there, depending on the chosen system.

The source control interface is implemented in PADS I/O Designer using TCL interface. It is possible to add the support for another source control system by editing a TCL script. The list in the Settings dialog contains the custom item. Selecting this item turns on the interface described in the scc_custom.tcl file, located in the tcl subdirectory of the PADS I/O Designer installation directory. The comments on the scc_custom.tcl file contain the details on customizing.

The main advantage of using source control is to have a repository, which stores the base version of the database. Designers do not modify the database directly in the repository, but rather work on the local copy. The usual way to utilize Source Control is to get the database from the repository, and store it in the local directory. The database will be read-only and may be reviewed. If a designer wants to make some changes in the database, the database should be checked-out, which means that the database is marked in the repository as being modified by the designer. Only one designer may modify the database at a time. After completing changes, the database may be checked-in to the repository, creating a new version of the stored database. PADS I/O Designer integrates support to check-in and check-out databases, review database history, and so on.