Bug 293453 - Sharing a single project using Quick Access
Summary: Sharing a single project using Quick Access
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 293447
Blocks:
  Show dependency tree
 
Reported: 2009-10-27 11:10 EDT by Mykola Nikishov CLA
Modified: 2019-09-06 15:30 EDT (History)
0 users

See Also:


Attachments
Proposed implementation (9.46 KB, patch)
2009-10-27 11:14 EDT, Mykola Nikishov CLA
no flags Details | Diff
Proposed implementation in action (43.77 KB, image/png)
2009-10-27 11:16 EDT, Mykola Nikishov CLA
no flags Details
Patch v02 (11.29 KB, patch)
2009-10-30 06:51 EDT, Tomasz Zarna CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Mykola Nikishov CLA 2009-10-27 11:10:42 EDT
Sharing a single project using Quick Access with a keyboard from almost any place of the workspace seems to me as a convenient approach:
- activate Quick Access (which is bound to Ctrl+3 by default)
- typing SU (which means 'share using') followed with a first letter from provider's name ('C' for a CVS team provider) will provide you with a list of all currently open projects not connected to any team provider grouped by provider
- select a project
- associates a project with a given team provider using a wizard dialog declared in org.eclipse.team.ui.configurationWizards extension point for a selected team provider and which extends IConfigurationWizard.

This implementation was adapted from my initial contribution to EGit project, see bug#291283. Also in its current state it depends on an enhancement requested in bug#293447. I'll modify it accordingly if bug#293447 wouldn't be accepted.
Comment 1 Mykola Nikishov CLA 2009-10-27 11:14:11 EDT
Created attachment 150642 [details]
Proposed implementation

This patch is against 3.5.0.I20090430-0408. Source code was imported using Plug-ins view's context menu 'Import as' - 'Source project'.
Comment 2 Mykola Nikishov CLA 2009-10-27 11:16:30 EDT
Created attachment 150643 [details]
Proposed implementation in action
Comment 3 Tomasz Zarna CLA 2009-10-30 06:51:42 EDT
Created attachment 150910 [details]
Patch v02

Thanks for the patch Mykola, here is an updated version which can be flawlessly applied to HEAD. I will take a look at it during 3.6M4, all right?
Comment 4 Mykola Nikishov CLA 2009-10-30 08:18:41 EDT
Tomasz, I'm ok about 3.6M4.

BTW, you left Share_single_project_command.name's value as is, 
https://bugs.eclipse.org/bugs/attachment.cgi?id=150910&action=diff#plugin.properties_sec1. But in this form it depends on bug#293447. Are you sure it'll be accepted? If it wouldn't user will see 'Share using {0}' as command's name which is not good.
Comment 5 Tomasz Zarna CLA 2009-11-06 09:46:01 EST
I didn't look at the code back then, just made sure it applies and compiles.
Comment 6 Mykola Nikishov CLA 2010-02-07 05:31:41 EST
Tomasz, is there any progress?
Comment 7 Tomasz Zarna CLA 2010-03-09 11:42:48 EST
I would like to see the blocker fixed first.
Comment 8 Mykola Nikishov CLA 2010-03-16 04:35:14 EDT
Tomasz, right now provided patch depends on bug#293477. But the only reason for a such dependency is to provide command's name using placeholders in form of 'Share using CVS' where 'CVS' is substituted dynamically.

As I have said before, this can be easily changed in a way that command's name will be in the form of 'Share project (Project: A; Provider: CVS)' in order to break dependency on bug#293477. Does it make sense in M7 timeframe? What is the best way?
Comment 9 Eclipse Webmaster CLA 2019-09-06 15:30:38 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.