Views

Important: The term view is used here in terms of the Eclipse UI. This term should not be confused with the StarTeam usage of view. In StarTeam, a view consists of an application folder tree view and the items associated with each folder in that tree.

You can access the StarTeam views by performing one of the following:

Selecting Window > Show View and selecting the desired view from the menu.
Selecting Window > Show View > Other and selecting the desired view from the StarTeam tree node.

When opening any of the perspectives or views, a main menu command displays along with additional StarTeam-specific toolbar buttons.

When you create a project, an initial or root view of that project is also created. This initial view, which has the same name as the project, consists of the root folder and a tree view of the child folder. It is always read/write.

The root view is called a dynamic view, because it shows all items in the project as they change, making it ideal for collaborative development.

To accommodate both user and project needs, however, the application enables you to create additional views of a project based on this view. These additional views may contain some or all of the contents of the original view and may behave differently.

For example, you might use views to:

Implement the same folder tree for both the 2.5 release and the 3.0 release of a product. The easiest way to do this is by creating a new view for the 3.0 release based on the view used for the 2.5 release.
Limit the portion of the project that certain team members see. Developers might need to see only the project's source code folder and its child folders; marketing personnel might need to see only the marketing folder and its child folders; and so on. Each of these views can have a different folder as its root.
Support branching and parallel development. By branching files and other data in a new view, you organization can start to work on the 2.0 version of a product without hampering the creation of service packs for the 1.0 version.

Views represent configurations of items and support different development baselines of the same code base. If desired, views can be compared and merged. For example, you might want eventually to merge files from 4.5 Maintenance and 5.0 New Development into the Baseline view. Views are highly flexible. For example, they can be re-configured to show items as they existed at an earlier point in time or based on a view label or associated promotion state. Rollback views are read-only, as they show a precise state of the items, and no longer permit changes.