Bug 210646 - [History View] Enhancements for copying tag action in CVS Resource History view
Summary: [History View] Enhancements for copying tag action in CVS Resource History view
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on: 87752
Blocks:
  Show dependency tree
 
Reported: 2007-11-22 07:19 EST by Jakub Jurkiewicz CLA
Modified: 2019-09-06 15:36 EDT (History)
2 users (show)

See Also:


Attachments
Patch (7.36 KB, patch)
2007-11-27 06:52 EST, Jakub Jurkiewicz CLA
no flags Details | Diff
Patch (2.94 KB, patch)
2007-11-28 07:12 EST, Tomasz Zarna CLA
no flags Details | Diff
Patch (3.41 KB, patch)
2007-11-29 06:20 EST, Jakub Jurkiewicz CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jakub Jurkiewicz CLA 2007-11-22 07:19:58 EST
This bug was distinguished from the bug #87752. The action for copying tags in the CVS Resource History view should:
1) have a key binding defined,
2) allow multiple selection in the tag table viewer,
3) have "Select all" and "Deselect all" actions in the context menu.
Comment 1 Tomasz Zarna CLA 2007-11-22 11:30:12 EST
As I said in the bug 87752, I would be happy to see these done. It's the little things that make us smile while working with Eclipse, isn't it?
Comment 2 Jakub Jurkiewicz CLA 2007-11-27 06:52:58 EST
Created attachment 83858 [details]
Patch

I'm attaching a patch, but there are two problems:
1) What should be copied to the clipboard when more then two tags are selected? e.g. we have tags:
"Tag 1
Tag 2"
I thought about "Tag1\nTag2" but this doesn't seem to work (there is a problem with \n). However, maybe this should be handled in some other way?
2) How should the key bindings be defined? I guess that the actions should be registered, but didn't find any good solution? Tomasz could you give me some hint?
Comment 3 Tomasz Zarna CLA 2007-11-28 07:12:43 EST
Created attachment 83967 [details]
Patch

Patch with some adjustments to your TableViewerAction -- this is my answer to 1) from the previous comment
Comment 4 Tomasz Zarna CLA 2007-11-28 07:40:33 EST
As for your second question, I'm afraid what I can give you will be only a hint. I hope it will help.
So, this is what I would do:
* set Action definition for the Copy Tag action - ie. copyTagAction.setActionDefinitionId(IWorkbenchActionDefinitionIds.COPY);
* register the action - actionBars.setGlobalActionHandler(ActionFactory.COPY.getId(), copyTagAction);

But I may be missing something. You can take a look at this page (and its "See Also"s):
http://wiki.eclipse.org/FAQ_How_do_I_make_key_bindings_work_in_an_RCP_application%3F

The other thing I would like to mentioned is the "Deselect All" button. On second thought it's not a good (neither common) idea to place such an action in the context menu. I think "Select All" will be enough, but still, this seems to be a standard workbench action so we could use a keybinding here too.
	 
Comment 5 Jakub Jurkiewicz CLA 2007-11-29 06:20:33 EST
Created attachment 84051 [details]
Patch

Thanks for the patch for TableViewerAction, now it looks much better.
I used your hints according key bindings, but there is a problem I encountered earlier: there are already registered actions (copying and selecting all) for the comment window (textViewer), so which actions should be active: those for tags or those for comment? 
Any suggestions?
Comment 6 Tomasz Zarna CLA 2007-12-10 12:33:11 EST
The patch still needs some improvements in order to release it to HEAD (and mark as FIXED). We will try to work it out during M5.
Comment 7 Jakub Jurkiewicz CLA 2008-02-06 04:58:43 EST
Can we move it to M6? I should have time o finish this up.
Comment 8 Szymon Brandys CLA 2008-02-06 05:16:56 EST
I'm removing the target milestone. When the patch is ready we can set it again appropriately.

Jakub, it wouldn't look good, if the bug was postponed again. I'm looking forward to the fix. Thanks.
Comment 9 Tomasz Zarna CLA 2008-02-06 10:15:32 EST
Comment on attachment 83967 [details]
Patch

Marking the second patch as obsolete - I've logged a separate bug for it (see bug 218008).
Comment 10 Eclipse Webmaster CLA 2019-09-06 15:36:32 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.