Perforce support readme file

General information

    This document covers issues with supporting Perforce with SCC interface.

    Integration with Perforce was tested with client version 99.1.10232,
    server version: 99.1/11533 (1999/07/29)

Known issues and problems

    Default Perforce project name produced by Together starts with \\depot 
    prefix. Browse VCS project button doesn't work with this provider.
    
    To be able to work with this provider user should place all Together
    project to be used with Version Control under client root directory
    which can be changed in Perforce Client. Read Perforce documentation for 
    more detailed information about this process.

    Created Perforce project has the same name as Together project directory
    even if user changes it in Together project properties. Perforce have 
    no ability to create subProject with arbitrary name so all the Perforce 
    project names are the same as the local directory names where corresponding 
    files are stored.

    Perforce does not support Remove and Get commands, so these actions, which
    are available in Version Control/System dialog, do nothing.
