| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML> |
| <HEAD> |
| <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"> |
| <META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css"> |
| |
| <LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> |
| <TITLE>Building a team UI</TITLE> |
| |
| <link rel="stylesheet" type="text/css" HREF="../book.css"> |
| </HEAD> |
| <BODY BGCOLOR="#ffffff"> |
| <h2> |
| Building a team UI |
| </h2><p> |
| The team UI plug-in is based on the philosophy that the team subsystem should |
| provide simple hooks and slots for providers to add their UI |
| implementation. Rather than define standard team operations, the team |
| plug-in leaves the workflow up to the provider implementation. The team |
| UI implements a few standard wizards and dialog pages that providers can |
| enhance, such as the project configuration wizard, the project set export |
| dialog, and the preferences for file types and ignored files. More |
| importantly, it also defines a |
| "Team" slot for actions and preferences that serve as a single |
| point of integration for UI contributed by provider's. In this way, the |
| user learns where to find all team related function. |
| </p> |
| <p>To build a team UI, you must start with basic design work. Identify the actions that your |
| repository supports and in what views and editors these actions should be accessible. The implementation for your UI is done with the <a href="workbench_basicext.htm">standard |
| workbench extension points</a>. In addition, you can define your own |
| preferences which plug in to the standard framework. You may even need to |
| build your own views to present repository specific information and operations. |
| (The CVS client implements its own views for synchronizing with the repository |
| and navigating the repository.) |
| </p> |
| <p>In short, building a team UI involves knowledge of a few team-specific UI |
| classes, but is mostly accomplished using workbench UI design and development |
| principles. |
| </p> |
| |
| |
| |
| |
| <p><a href="../hglegal.htm"><img border="0" src="../ngibmcpy.gif" alt="Copyright IBM Corporation and others 2000, 2003." border="0" width="324" height="14"></a></p> |
| </BODY> |
| </HTML> |
