About Perforce

Because Lingo uses an open architecture, Lingo projects are compatible with all source control systems. In addition to this native support for all source control applications, Lingo provides integrated support with some source control applications.

Please reference the source control topics in this section if you are using Lingo's integrated source control with Perforce.

Following are definitions for some of the common phrases used in Lingo's integrated source control with Perforce.

Bind This means to connect your project to Perforce. After doing this, you can then take advantage of all the automated source control tasks (such as submit, revert, lock, unlock, and so on).

Submit This means to send changes made to your open Lingo files to the server, or depot.

Check Out This means to copy the latest source control files to your local Lingo project and remove the "Read Only" designation from them so that you can edit the files.

Get Latest Version This means to copy the latest source control files to your local project without necessarily checking out the files. This means that the "Read Only" designation will remain associated with the files until you check them out.

Revert This means to undo changes you have made to a Lingo file. Changes are reverted to the way they were at the last submit.

Lock This means to prevent other users from submitting changes to an opened Lingo file in source control.

Unlock This means to remove an existing lock from an open Lingo file so other users can submit changes to the file.

Note: Lingo integrates with multiple source control providers to provide built-in source control support. Each of the source control providers built-in to Lingo uses different terms. As such, Lingo's source control interface is different depending on which source control provider you use. Please refer to the sections for each source control provider if you need to see information about the terms used by other built-in systems.

This indicates that you have a file in your project but have not yet submitted it to Perforce. This might occur if you import a Lingo project from source control and have not yet checked in your files to the server, or if you update a project and new files are added from the source project. To resolve this, simply right-click on the file(s) and select Source Control > Submit. See Submitting Source Control Files—Perforce.

Not Checked Out

This indicates that the file is added to source control but is not currently checked out, which means that it contains a "Read Only" designation in its properties. In order to edit the file, you must check it out from source control. See Checking Out Source Control Files—Perforce.

Locked by Another User

This indicates that another user has locked the file. You will often see this icon in conjunction with the icon, indicating that another user is both using the file and has locked the file. You can still make changes to this file even if another user has locked it, but you cannot submit them until the lock is removed. See Locking a File—Perforce and Unlocking a File—Perforce.

Locked by You

This indicates that you have locked the file. You will often see this icon in conjunction with the icon, indicating that you have both locked and checked out the file. Other users can make changes to this file even if you have locked it. See Locking a File—Perforce and Unlocking a File—Perforce.

Checked Out to Other User

This indicates that the file is currently checked out by another user. You will often see this icon in conjunction with the icon, indicating that another user is both using the file and has locked the file.

Following are the basic steps for using Lingo's source control integration for a multi-user team.

Set Up Perforce Install Perforce and set up the database and any folders where you want to place the project. Also, assign permissions to the proper individuals. This task may be performed by someone else, such as a network administrator.

In Lingo, do one of the following, depending on whether you are creating a new Lingo project or using an existing one.

Create and Bind New Project Create a new Lingo project and simultaneously bind it to an integrated source control application. See Creating New Projects.

OR

Bind Existing Project If you have an existing Lingo project on your local machine, bind the project to the source control application. See Binding a Project to Perforce.

Note: Only one of the users needs to perform this task. The other users on the team can follow Step 3 below.

Import Project Other users on the team can easily import the project from source control. This creates a copy of the Lingo project on the user's computer. See Importing a Project from Perforce.

Get Latest Version After you bind a Lingo project to a source control application, you can get the latest version of any of the source control files. When you do this, you are copying the most current files stored in the source control application to your local Lingo project without necessarily checking out the files. This means that the "Read Only" designation will remain associated with the files until you check them out. When working with other users, it is a good idea to do this frequently (e.g., at the beginning of each day) in order to ensure you have the latest changes that those users have made, and that they have the latest changes you've made. See Manually Getting the Latest Version of Source Control Files—Perforce.

Check Out Files When you need to work on any of the Lingo project files, you can check them out. Checking out files means to copy the latest source control files to your local Lingo project and remove the "Read Only" designation from them so that you can edit the files. A red check mark is displayed next to each file that is checked out. See Checking Out Source Control Files—Perforce.

Lock/Unlock Files When you are working, you may want to lock the files you have modified. Locking a file does not prevent other users from modifying the file. However, no one else can submit a file that you have locked until you remove the lock. See Locking a File—Perforce and Unlocking a File—Perforce.

Submit Files When you are finished editing files, you can submit them to source control. Submitting a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically submit files so that you have a backup in source control. See Submitting Source Control Files—Perforce.

Merging There may be times when you need to merge changes from different users when checking in a file. The merge occurs automatically if there are no conflicting changes (i.e., changes do not occur in the same location). If there are conflicting changes, a dialog opens, allowing you to determine how changes are merged. See Merging Source Control Files—Perforce.

Following are the basic steps for using Lingo's Perforce integration for a single user.

Set Up Perforce Install Perforce and set up the database and any folders where you want to place the project. Also, assign permissions to the proper individuals. This task may be performed by someone else, such as a network administrator.

In Lingo, do one of the following, depending on whether you are creating a new Lingo project or using an existing one.

Create and Bind New Project Create a new Lingo project and simultaneously bind it to an integrated source control application. See Creating New Projects.

OR

Bind Existing Project If you have an existing Lingo project on your local machine, bind the project to the source control application. See Binding a Project to Perforce.

Check Out Files When you need to work on any of the Lingo project files, you can check them out. Checking out files means to copy the latest source control files to your local Lingo project and remove the "Read Only" designation from them so that you can edit the files. A red check mark is displayed next to each file that is checked out. See Checking Out Source Control Files—Perforce.

Submit Files When you are finished editing files, you can submit them to source control. Submitting a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically submit files so that you have a backup in source control. See Submitting Source Control Files—Perforce.

Following are some additional tasks and features related to source control.

Automatic Status Checks If you are using source control integration in Lingo, you can check for frequent status changes automatically. You can specify the number of minutes and seconds when you want Lingo to ping the source control repository and get status changes for files that have been checked out, checked in, moved, deleted, etc. The upside of this feature is that you can ensure that the source control status information is always up to date. The downside is that you may experience slower performance due to this constant communication over the network. See Enabling Source Control Status Checks—Perforce.

Disable Prompt for Get Latest By default, when you open a project that is bound to source control, a message automatically asks if you want to get the latest version of files. However, you can disable this prompt in the Options dialog. See Disabling the Get Latest Prompt for Source Control—Perforce.

Disconnect from Source Control There may be times that you need to disconnect from source control to work offline. You can disconnect from source control and reconnect at any time. See Disconnecting from Source Control—Perforce.

Version Displays a number for each version of the file. The lower the number, the older the version. The higher the number, the more recent the version.

Users Displays the name of the user who has been working on the file.

Date Displays the date and time when the action has occurred.

Action Displays the action that has taken place for the file (e.g., submit).

Comment Displays the comment (if any) associated with the file. A comment can be added to a file when you submit that file to source control. This enables you to maintain an audit trail for the file's history.

Show Differences Opens a dialog that lets you view the differences between two versions of a file. If you select one row in the History dialog and view the differences, you will see the content differences between the version that you selected and the version of the file in your local copy of the Lingo project. If you select two files in the History dialog (by holding down the CTRL key) and view the differences, you will see the content differences between those two versions of the file.

Locks You can lock files so that other users cannot submit those same files when you have them checked out. You might use this feature to prevent conflicting changes from occurring and having to merge files as a result. You can set files to be locked automatically when you check out files. This can be done from the Options dialog (Source Control tab). Another option is to manually set files to be locked whenever you check out files. This can be done from the Check Out dialog. See Checking Out Source Control Files—Perforce, Locking a File—Perforce, and Unlocking a File—Perforce.