platform-core-home/plan_team_integration.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.2 - (view) (download) (as text)

1 : dj 1.1 <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
2 :     <html>
3 :     <head>
4 :     <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
5 :     <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
6 :     <title>Team/Resource Integration Details</title>
7 :     <link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css">
8 :     </head>
9 :     <body text="#000000" bgcolor="#FFFFFF">
10 :     &nbsp;
11 :     <table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
12 :     <tr>
13 :     <td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b><font face="Arial,Helvetica"><font color="#FFFFFF">Team/Resource
14 :     Integration Details</font></font></b></td>
15 :     </tr>
16 : dj 1.2 <tr>
17 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
18 :     <td WIDTH="98%">
19 :     <p><b>Description</b></p>
20 :     <p>Described in detail on the <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/docs/online/team3.0/resources.html">Platform/Team
21 :     team web</a> site.</p>
22 :     <p>See also bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37722">37722</a>.</p>
23 :     <p>&nbsp;</p>
24 :     </td>
25 :     </tr>
26 : dj 1.1 <tr>
27 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
28 :     <td WIDTH="98%">
29 : dj 1.2 <p><b>Questions and Issues</b></p>
30 : dj 1.1 <ul>
31 :     <li>How to manage the file system provider mapping to the resources?
32 :     <ul>
33 :     <li>Needs to be performant.</li>
34 :     </ul>
35 :     </li>
36 :     <li>How is this information persisted?</li>
37 :     <li>Should this information be shared in the repository?</li>
38 : dj 1.2 <li>How do we store folder-level metadata? (do we need to do this?)
39 :     <ul>
40 :     <li>If so, then what differentiates a project from a folder?</li>
41 :     </ul>
42 :     </li>
43 : dj 1.1 <li>How do we handle linked resources?</li>
44 :     <li>How do we provide access to the Core library calls?</li>
45 :     <li>Do we need startup/shutdown lifecycle events to allow for cleanup?</li>
46 :     <li>How do we deal with missing providers?</li>
47 :     <li>DefaultProvider could be an abstract class for others to inherit from.</li>
48 :     <li>Register data providers via an extension point.</li>
49 : dj 1.2 <li>The relationship between TeamProviders and DataProviders is yet to
50 :     be defined, but we would like to keep knowledge team out of Core as
51 :     much as we can. It is thought that perhaps TeamProviders should be able
52 :     to answer their &quot;preferred data provider&quot;.</li>
53 :     <li>Take a look at the current Move/Delete hook implementation. With this,
54 :     there are basically 2 ways of doing things. You can either do some pre-processing
55 :     and then defer the actual operation to the default (by calling IResourceTree.standardFileDelete,
56 :     etc) or the operation is broken into 2 separate pieces. The implementor
57 :     of the Move/Delete hook performs the file-system based part of the function
58 :     and then makes the appropriate calls back into the resource tree in
59 :     order to update the workspace.</li>
60 : dj 1.1 </ul>
61 :     <p>&nbsp;</p>
62 :     </td>
63 : dj 1.2 </tr>
64 :     <tr>
65 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
66 :     <td WIDTH="98%">
67 :     </td>
68 : dj 1.1 </tr>
69 :     </table>
70 :    
71 :     </body>
72 :     </html>