In PocketBuilder you can set up a source control connection profile at the workspace level only. Local and advanced connection options can be defined differently on each machine for PocketBuilder workspaces that contain the same targets.
Local connection options allow you to create a trace log to record all source control activity for your current workspace session. You can overwrite or preserve an existing log file for each session.
You can also make sure a comment is included for every file checked in to source control from your local machine. If you select this connection option, the OK button on the Check In dialog box is disabled until you type a comment for all the objects you are checking in.
The following table lists the connection options you can make for each local connection profile:
Select this option |
To do this |
|---|---|
Log All Source Management Activity (not selected by default) |
Enable trace logging. By default the log file name is PKSCCxx.LOG, where xx is the PocketBuilder version number. The log file is saved in your workspace directory, but you can select a different path and file name. |
Append To Log File (default selection when logging is enabled) |
Append source control activity information to named log file when logging is enabled. |
Overwrite Log File (not selected by default) |
Overwrite the named log file with source control activity of the current session when logging is enabled. |
Require Comments On Check In (not selected by default; not available for PBNative source control) |
Disable the OK button on the Check In dialog box until you type a comment. |
This Project Requires That I Sometimes Work Offline (not selected by default) |
Disable automatic connection to source control when you open the workspace. |
Delete PowerBuilder Generated Object Files (not selected by default) |
Remove object files (such as SRDs) from the local directory after they are checked in to source control. This may increase the time it takes for PocketBuilder to refresh source control status, but it minimizes the drive space used by temporary files. You cannot select this option for the Perforce, ClearCase, or Continuus source control systems. |
Perform Diff On Status Update |
Permit display of out-of-sync icons for local objects that are different from objects on the source control server. Selecting this also increases the time it takes to refresh source control status.You cannot select this option for Perforce. |
Suppress prompts to overwrite read-only files |
Avoid message boxes warning that read-only files exist on your local project directory. |
Status Refresh Rate (5 minutes by default) |
Specifies the minimum time elapsed before PocketBuilder automatically requests information from the source control server to determine if objects are out of sync. Valid values are between 1 and 59 minutes. Status refresh rate is ignored when you are working offline. |
Advanced connection options depend on the source control system you are using to store your workspace objects. Different options exist for different source control systems.
Applicability of advanced options
Some advanced options might not be implemented or might be
rendered inoperable by the PocketBuilder SCC API interface. For
example, if an advanced option allows you to make local files writable
after an Undo Check Out operation, PocketBuilder still creates read-only
files when reverting an object to the current version in source
control. (PocketBuilder might even delete these files if you selected
the Delete PowerBuilder Generated Object Files option.)
To set up a connection profile:
Right-click the Workspace object in the System Tree (or in the Tree view of the Library painter) and select Properties from the pop-up menu.
Select the Source Control tab from the Workspace Properties dialog box.
From the Source Control System drop-down list, select the system you want to use.
Only source control systems that are defined in your registry (HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\ InstalledSCCProviders) appear in the drop-down list.
Type in your user name for the source control system.
Some source control systems use a login name from your registry rather than the user name that you enter here. For these systems (such as Perforce or Version Manager), you can leave this field blank.
Click the ellipsis button next to the Project text box.
A dialog box from your source control system displays. Typically it allows you to select or create a source control project.
The dialog box displayed for PBNative is shown below:
Fill in the information required by your source control system and click OK.
The Project field on the Source Control page of the Workspace Properties dialog box is typically populated with the project name from the source control system you selected. However, some source control systems (such as Perforce and Vertical Sky) do not return a project name. For these systems, you can leave this field blank.
Type or select a path for the local root directory.
All the files that you check in to and out of source control must reside in this path or in a subdirectory of this path.
(Option) Select the options you want for your local workspace connection to the source control server.
(Option) Click the Advanced button and make any changes you want to have apply to advanced options defined for your source control system.
The Advanced button might be grayed if you are not first connected to a source control server. If Advanced options are not supported for your source control system, you see only a splash screen for the system you selected and an OK button that you can click to return to the Workspace Properties dialog box.
Click Apply or click OK.
