Home
Developing
Learn how to develop software with HCL VersionVault and HCL VersionVault Remote Client.
Developing software with HCL VersionVault
HCL VersionVault provides a flexible set of tools that your organization uses to implement its development and change management policies.
Views
About text modes for views
Guidelines for view text modes

Developing
Learn how to develop software with HCL VersionVault and HCL VersionVault Remote Client.
- Developing software with HCL VersionVault
  HCL VersionVault provides a flexible set of tools that your organization uses to implement its development and change management policies.
  - Elements
  - Views
  - VOBs
  - HCL VersionVault Windows Explorer
  - cleartool command-line interface
  - Software development with base VersionVault
  - Software development with UCM
  - Workflow for disconnected use
  - To add shortcuts to your Windows Send To folder
  - Developer tools
    Learn about the developer tools provided by HCL VersionVault for you to use to implement your development and change management policies.
- Developing software with HCL VersionVault Explorer
  HCL VersionVault provides two clients for software developers: local and remote. Each client supports different mechanisms for accessing source-controlled filesystem objects. Both clients provide graphical and command-line interfaces.

Guidelines for view text modes

Any policy governing access to VOBs based on the text mode of a view is not enforced. However, a user who edits a file in a view that has the "wrong" text mode configuration can cause problems for other users who need to edit that file. If all developers at your site are using the same development platform (Windows® or Linux or UNIX) or use tools that are compatible with either platform line-termination convention, all views should be created in transparent text mode.

Most sites with a mix of Windows® and Linux or UNIX development platforms should adopt a policy that allows users of the primary development platform to create views in transparent text mode, and limits the use of strip_cr or insert_cr text modes for the minority of platforms that require different line-termination conventions. If most users are developing software on Linux or UNIX systems:

Linux and UNIX clients should use views created in transparent text mode.
Windows® clients should use views created in insert_cr text mode.

If most users are developing software on Windows® systems:

Windows® clients should use views created in transparent text mode.
Linux and UNIX clients should use views created in strip_cr text mode.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.