Summary: | [API] Common Team Repository browser view | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Brock Janiczak <brockj> | ||||
Component: | Team | Assignee: | Platform Team Inbox <platform-team-inbox> | ||||
Status: | ASSIGNED --- | QA Contact: | |||||
Severity: | enhancement | ||||||
Priority: | P5 | CC: | ekuleshov, gunnar, konstantin, krtaylor, mn, wmitsuda | ||||
Version: | 3.2 | Keywords: | helpwanted | ||||
Target Milestone: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Brock Janiczak
2006-04-26 05:40:13 EDT
Yes, I agree that now (or at least 3.3) is the time to look at this again. Created attachment 39546 [details]
team synchronizing perspective screenshot
I agree with the description, and see the two views in the attached screenshot as redundant. I also think that the platform 'encouraging' a different perspective for each version control system will result UI bloat, and hope that this would make the seperate CVS and SVN synchronizing perspectives go away in favor of a more flexible Team Synchronizing perpective.
There is currently no plan to address this issue. Defining the view would not be much work (i.e. we would use the Common Naviogator framework) but converting the CVS Repositories view content would be a bit of work and we just don't have the cycles to do it. Can we at least get that view definition? Then CVS provider can be converted later as a separate issue (perhaps somebody else may work on a patch). See Bug 252239 which aims to create a Common Servers View where app servers, databases, code repositories, etc. can all be represented. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. |