Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360804 - key bindable command for edit with xtext editor
Summary: key bindable command for edit with xtext editor
Status: RESOLVED WORKSFORME
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.8.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-13 08:02 EDT by Nicolas Bros CLA
Modified: 2011-10-18 04:53 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Bros CLA 2011-10-13 08:02:25 EDT 
The xtext editors (for editing a Property for example) are much faster to use than clicking through multiple properties and modal dialogs.

But to open them, we currently have to:
- select the Property in a diagram
- right click on it
- navigate to "Edit Property"
- click on "Using Advanced Property Textual Editor Editor"

I would rather use a (preferably user-definable) key binding for this. For example F2 (replacing the editor for the name only), or Shift+F2 (in order to keep both editors accessible).
Comment 1 Camille Letavernier CLA 2011-10-14 03:46:59 EDT 
Hello Nicolas,

The Papyrus Preferences allow you to define the X-Text editor as the default editor:

Preferences -> Papyrus/Embedded Editors
Comment 2 Nicolas Bros CLA 2011-10-14 03:58:11 EDT 
Thank you for the tip!
Comment 3 Nicolas Bros CLA 2011-10-14 04:01:32 EDT 
Now I wish it would work with Operations too. 
I see o.e.p.operation.editor.xtext* in trunk/extraplugins/alf on the Papyrus SVN. Am I supposed to install this plug-in separately, or it is an incubating component that you are going to put in a future release?