Better customization of run/debug keyboard shortcuts

[jokester01au]

I want to have the run/debug keyboard shortcuts to be the same when I am debugging XSLT as when I am debugging Java.

the XSLT debugger shortcuts are present in the "keys" preferences section, which is great, but I can't access an appropriate context to set them in. What I want is a "Oxygen perspective" context (or two separate ones for xml/xslt/xquery if required). Then I can customise it so that when I am in the java editor/debugger perspective pressing F12 will launch my most recent java program, but if I am in an oxygen perspective, pressing F12 will launch the xslt/xquery debugger.

The best that I can currently do is "editing XSLT", which kinda works, but not very well. If the current focus is on one the xml file, or one of the variables/xwatch/etc/etc views, then the keys revert to the global action, which means I often inadvertently launch a java program, which gets very irritating.

So, I'd like appropriate entries added to the "when" list so that I can scope the oxygen keyboard shortcuts correctly.

Regards,
Joe.

[sorin_ristache]

Hello,

All the actions of the oXygen debugger that can be configured in Preferences -> General -> Keys have the XSLT Debugger category. For example if you change the shortcut of Step In from the default shortcut F5 to other shortcut for example Ctrl+Shift+F5 the new shortcut executes Step In when you are in the XSLT Debugger perspective. It does not matter the view or the editor that has the focus when you use the shortcut.

It is not possible to run the most recent transformation with a shortcut as you can run the most recent Java application in the Java perspective because the oXygen plugin does not create a Run/Debug configuration with the settings of the XSLT transformation executed in the debugger. We will consider creating a Run/Debug configuration with the settings of a transfromation scenario in a future version of the plugin.


Regards,
Sorin

[jokester01au]

for example Ctrl+Shift+F5 the new shortcut executes Step In when you are in the XSLT Debugger perspective. It does not matter the view or the editor that has the focus when you use the shortcut.

This is not correct. "Category" merely groups the various commands together. You'll notice that cut and paste have the "Edit" category. That does not say anything about when their assigned shortcut(s) will or won't be active. The latter information is provided by the "When" setting, which has a large number of contexts in which the shortcut could be active.

I have just now tried setting the "Run" command in the "XSLT Debugger" category to the same shortcut and scope as the "Run" command in the "Run/Debug" category. Doing so gives me a binding conflict, and when I press the shortcut (while in XSLT debugging perspective) nothing happens.

I'm not suggesting that you create run configurations, I'm suggesting something much simpler, which is to create a "Oxygen" option for the "When" listing, that is active whenever in an oxygen perspective or view.

You currently have "Oxygen XML Editor General", which goes some of the way, but if you are focused on the XWatch or other similar views then that "When" option is not active. I think that you should just broaden the scope of this option.

Regards,
Joe.

[sorin_ristache]

I'm not suggesting that you create run configurations, I'm suggesting something much simpler, which is to create a "Oxygen" option for the "When" listing, that is active whenever in an oxygen perspective or view.

You currently have "Oxygen XML Editor General", which goes some of the way, but if you are focused on the XWatch or other similar views then that "When" option is not active. I think that you should just broaden the scope of this option.

Yes, we should add a scope that covers all the editors and views of the oXygen Debugger perspective. We will try to define such a scope in the oXygen plugin. Usually the scope is at the editor level, at the view level or very general ('In Windows') but the last one creates a conflict with the action with the same name of the Eclipse JDT as you noticed.


Regards,
Sorin