Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 364858

Summary:	Support keybindings for common sapphire actions, e.g. MoveUp,MoveDown,
Product:	z_Archived	Reporter:	Greg Amerson <gregory.amerson>
Component:	Sapphire	Assignee:	Project Inbox <sapphire.ui-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	konstantin
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Greg Amerson

2011-11-25 12:12:55 EST

When working with sdef editor on a large file, and I wish to move a node in the outline view, I find myself wishing there were keybindings for moveup/movedown instead of having to access the action via context-menu each time.

Comment 1 Konstantin Komissarchik

2011-11-28 13:37:16 EST

These key bindings do exists... CTRL+ALT+SHIFT+ up or down arrow

Comment 2 Greg Amerson

2011-11-28 17:01:16 EST

Are these configurable?  I'm on linux and those keybindings are taken by the host OS virtual window manager.  Is there a way to re-map the sapphire actions to another combination?

Comment 3 Konstantin Komissarchik

2011-11-28 21:22:06 EST

The key bindings are currently not user configurable. They are defined as part of action definition in sapphire-extension.xml or sdef. 

Perhaps key bindings should be left for the presentation layer instead. In Eclipse IDE and probably Eclipse RCP, user expectation is to configure key bindings via Window -> Preferences -> General -> Keys, but that's presents a number of problems. For instance, if key bindings is a feature of RCP environment do we have no key bindings in plain SWT presentation? Another (bigger) issue is that Eclipse key bindings system relies on Eclipse extension system (plugin.xml), which requires singleton bundles, something that we are explicitly working to avoid in Sapphire. That is, we are trying to get to the point where multiple versions of Sapphire runtime bundles can exist concurrently in a single install. This would make it easier for us to continue to evolve Sapphire as needed while allowing the growing number of adopters the freedom to move to new versions at their own pace. Unfortunately, going this direction precludes using Eclipse extension system in any part of Sapphire runtime.

It's a difficult problem and I welcome ideas for how to improve the current key bindings story.