Launch the TeamWATCH 3D client
The following instructions are about how to use the TeamWATCH 3D client to see the project and monitor other’s activities on the same project to solve conflicts. You can launch the TeamWATCH visualization tool by clicking the TeamWATCH3D_win.exe in T:\TeamWATCH3D_Win. After that, you will see the main menu as shown in Figure 18, modify the server address to the address you got from the instructor and port number “8080”, then click “go” to view the visualization.
Figure 11 Open TeamWATCH visualization tool
After opening the visualization view, you will see the project’s CVS repository visualization in a 3D city metaphor as shown in Figure 12. Each blue pedestal represents a folder. Each set of cylinders indicates a file, and every small cylinder indicates a revision of this file. The cylinders in the same set are ordered by the revision time, the higher the cylinder, the closer the revision time to the current time. Different colors of small cylinders stand for different authors. You can use the file name filter, author name filter, and a revision number filter on the lower-left corner to filter out what you want on to see (you can combine these three filters to search specific revision of a specific file, etc).
Figure 12 TeamWATCH 3D city visualization of a project
Now you can monitor other’s activities on their own workspace about this project. When one of your teammates revised a file locally (but haven’t committed it), you will see a smoke rising from the top of the cylinder indicating that specific file as shown in figure 13 (different colors of smoking represent different authors). When you see a smoke rising, you should know that someone is changing the relevant file in their workspace but hasn’t committed his/her changes. At that time, if you happen to modify the same file locally, you can sync with the remote developer to know the remote changes and if remote changes will be in conflict with your local changes, you can try to find a way to avoid it such as working on other files first. If the remote changes on the same file have been committed, the smoke in the color representing the remote developer will disappear and a new cylinder will be added to represent the new revision of that file. After that, when you commits your changes to the same file, you may encounter the conflicts, and may need to merge the conflict manually (please refer to the section below for how to resolve the merge conflict)
Figure 13 Smoking indicates direct conflict of files