| 16 |
<tr> |
<tr> |
| 17 |
<td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td> |
<td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td> |
| 18 |
<td WIDTH="98%"> |
<td WIDTH="98%"> |
| 19 |
<p><b>Team/Resource Integration </b>(bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37722">37722</a>, |
<p><b>Description</b></p> |
| 20 |
described in detail <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/docs/online/team3.0/resources.html">here</a>)</p> |
<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 |
<p><i>Questions and Issues:</i></p> |
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> </p> |
| 24 |
|
</td> |
| 25 |
|
</tr> |
| 26 |
|
<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 |
|
<p><b>Questions and Issues</b></p> |
| 30 |
<ul> |
<ul> |
| 31 |
<li>How to manage the file system provider mapping to the resources? |
<li>How to manage the file system provider mapping to the resources? |
| 32 |
<ul> |
<ul> |
| 35 |
</li> |
</li> |
| 36 |
<li>How is this information persisted?</li> |
<li>How is this information persisted?</li> |
| 37 |
<li>Should this information be shared in the repository?</li> |
<li>Should this information be shared in the repository?</li> |
| 38 |
<li>What differentiates a project from a folder?</li> |
<li>How do we store folder-level metadata? (do we need to do this?) |
| 39 |
<li>How do we store folder-level metadata? (do we need to do this?)</li> |
<ul> |
| 40 |
|
<li>If so, then what differentiates a project from a folder?</li> |
| 41 |
|
</ul> |
| 42 |
|
</li> |
| 43 |
<li>How do we handle linked resources?</li> |
<li>How do we handle linked resources?</li> |
| 44 |
<li>How do we provide access to the Core library calls?</li> |
<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> |
<li>Do we need startup/shutdown lifecycle events to allow for cleanup?</li> |
| 46 |
<li>How do we deal with missing providers?</li> |
<li>How do we deal with missing providers?</li> |
| 47 |
<li>DefaultProvider could be an abstract class for others to inherit from.</li> |
<li>DefaultProvider could be an abstract class for others to inherit from.</li> |
| 48 |
<li>Register data providers via an extension point.</li> |
<li>Register data providers via an extension point.</li> |
| 49 |
|
<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 "preferred data provider".</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 |
</ul> |
</ul> |
| 61 |
<p> </p> |
<p> </p> |
| 62 |
</td> |
</td> |
| 63 |
</tr> |
</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 |
|
</tr> |
| 69 |
</table> |
</table> |
| 70 |
|
|
| 71 |
</body> |
</body> |