[JBoss JIRA] (JBIDE-16113) CLONE - Implement a 'Quick Access' Feature for Forge Commands
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-16113:
----------------------------------
Summary: CLONE - Implement a 'Quick Access' Feature for Forge Commands
Key: JBIDE-16113
URL: https://issues.jboss.org/browse/JBIDE-16113
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: forge
Reporter: Pavol Srna
Assignee: Koen Aers
Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1
Much like the Eclipse Quick Access Feature, pushing 'Cmd+4' should bring up a popup dialog with all the applicable commands. This involves creating a way for the Forge runtime and the Tools to communicate.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-9660) Cmd+4/Forge menu should be possible to activate without having the forge shell active
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9660?page=com.atlassian.jira.plugin... ]
Pavol Srna closed JBIDE-9660.
-----------------------------
> 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: 4.1.1.Alpha1
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16105) openshift-java-client: offer access to express.conf/timeout
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16105?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16105:
-------------------------------------
Summary: openshift-java-client: offer access to express.conf/timeout (was: openshift-java-client: offer access to timeout)
> openshift-java-client: offer access to express.conf/timeout
> -----------------------------------------------------------
>
> Key: JBIDE-16105
> URL: https://issues.jboss.org/browse/JBIDE-16105
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Fix For: 4.2.x
>
>
> express.conf now offers a setting for timeouts:
> {code}
> # The default timeout for network operations
> #timeout=<integer>
> {code}
> we currently offer direct access via identical key. Since *timeout* is a very common name we should most likely offer also prefixed access (ex. openshift.timeout).
> This should replace or be aliased by the system property we already use:
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16109) CLONE - Cmd+4/Forge menu should be possible to activate without having the forge shell active
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16109?page=com.atlassian.jira.plugi... ]
Pavol Srna resolved JBIDE-16109.
--------------------------------
Resolution: Done
> CLONE - Cmd+4/Forge menu should be possible to activate without having the forge shell active
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-16109
> URL: https://issues.jboss.org/browse/JBIDE-16109
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Fix For: 4.2.0.Alpha1
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-9660) Cmd+4/Forge menu should be possible to activate without having the forge shell active
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9660?page=com.atlassian.jira.plugin... ]
Pavol Srna updated JBIDE-9660:
------------------------------
Fix Version/s: (was: 4.1.1.Alpha1)
> 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: 4.2.0.Alpha1
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months