[jbosstools-issues] [JBoss JIRA] (JBIDE-9660) Cmd+4/Forge menu should be possible to activate without having the forge shell active
[
https://issues.jboss.org/browse/JBIDE-9660?page=com.atlassian.jira.plugin...
]
Koen Aers edited comment on JBIDE-9660 at 10/7/11 1:45 PM:
-----------------------------------------------------------
I have added the option to start the Forge runtime when Forge is not running and/or the
Forge view is not opened when Cmd+4 is pressed. It still brings the Forge view into focus
though. To make Cmd+4 work without the Forge view in focus involves a lot more work as -
at the moment - the runtime is linked to the view.
was (Author: koen.aers):
I have added the option to start the Forge runtime when Forge is not running and/or
the Forge view is not opened when Cmd+4 is pressed. It still brings the Forge view into
focus though. To make Cmd+4 work without the Forge view in focus involves a lot more work
as -at the moment- the runtime is linked to the view.
Cmd+4/Forge menu should be possible to activate without having the
forge shell active
-------------------------------------------------------------------------------------
Key: JBIDE-9660
URL: https://issues.jboss.org/browse/JBIDE-9660
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Reporter: Max Rydahl Andersen
Assignee: Koen Aers
Fix For: 3.3.0.M4
if the forge shell only is possible to show when the forge shell is in focus then its
just a fancy ctrl+space thing.
Should be able to call it from outside of the forge UI so it becomes easily accessible.
Challenge is though to ensure forge is in the right directory - but taking the current
selection as the directory to ensure forge is operating in should be enough.
Maybe the shell command should show the path for current selection so possible to know
what context it will be executed in ?
Possibly even provide a "breadcrumb" style ui allowing users to click on a path
segment to choose at what level it will operate.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira