Bug 138583 - [API] Common Team Repository browser view
Summary: [API] Common Team Repository browser view
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-04-26 05:40 EDT by Brock Janiczak CLA
Modified: 2019-09-06 15:36 EDT (History)
6 users (show)

See Also:


Attachments
team synchronizing perspective screenshot (56.13 KB, image/gif)
2006-04-26 11:51 EDT, Mik Kersten CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brock Janiczak CLA 2006-04-26 05:40:13 EDT
This bug is a follow on from bug 82435 which requested both a common history and repository browser.

To simplify the task of managing team connections for the user and reduce the need for custom team provider perspectives, it would be nice if Team could provide a common repository view for managing all team related connections.  With a repository view, history view and annotations in editors, most team funcionality is covered, which may allow for the creation of a team perspective.

This view could easily be implemented using the new common navigator that was added to the platform.  It may also be worth investigating showing team connections in the navigator as well, as this is the first view the user will see when opening Eclipse.

The actions that would be common across providers are create connection, refresh and collapse all.  Providers can add their own actions to the context menu of the view.  Team providers would have to supply an extension to show up in the new connection wizard.

This bug is not about making it easier to create new team providers, but to create a unified experience for the end user.
Comment 1 Michael Valenta CLA 2006-04-26 06:35:33 EDT
Yes, I agree that now (or at least 3.3) is the time to look at this again.
Comment 2 Mik Kersten CLA 2006-04-26 11:51:38 EDT
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.
Comment 3 Michael Valenta CLA 2006-08-17 11:17:46 EDT
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.
Comment 4 Eugene Kuleshov CLA 2006-08-18 16:32:58 EDT
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).
Comment 5 Konstantin Komissarchik CLA 2008-10-29 11:44:37 EDT
See Bug 252239 which aims to create a Common Servers View where app servers, databases, code repositories, etc. can all be represented.
Comment 6 Eclipse Webmaster CLA 2019-09-06 15:36:35 EDT
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.