[JBoss JIRA] (FORGE-2268) allow wizards in the CLI to let the user configure non-required inputs
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2268?page=com.atlassian.jira.plugin... ]
Work on FORGE-2268 started by George Gastaldi.
----------------------------------------------
> allow wizards in the CLI to let the user configure non-required inputs
> ----------------------------------------------------------------------
>
> Key: FORGE-2268
> URL: https://issues.jboss.org/browse/FORGE-2268
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.15.2.Final
> Reporter: James Strachan
> Assignee: George Gastaldi
> Fix For: 2.15.3.Final
>
>
> we're creating wizards for creating new camel components and endpoints. Pretty much all of these have a large number of possible input properties. However most of them are not required.
> I've hacked a multi-page wizard; the 2nd page adds all the non-required inputs to the builder. The CLI then ignores them all and accepts the default values ;)
> It would be nice if there a way prompt the user with something like...
> {code}
> Would you like to change any of the 12 inputs [Yn]:
> Y
> [1] foo
> [2] bar
> ...
> [12] thingy...
> 2
> enter the value for property bar with default value [123] :
> 456
> property bar set to 456
> Would you like to change any of the 12 inputs [Yn]:
> (repeat until n)
> {code}
> i.e. folks can just hit an extra enter to not bother entering any values, or they can keep hitting 'y' then picking the number of the input to change, then the value and enter
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 6 months
[JBoss JIRA] (FORGE-2296) Forge - Shell in CLI interactive mode, show * for required option and ? for optional
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2296?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2296.
----------------------------------
Fix Version/s: 2.15.3.Final
Resolution: Done
> Forge - Shell in CLI interactive mode, show * for required option and ? for optional
> ------------------------------------------------------------------------------------
>
> Key: FORGE-2296
> URL: https://issues.jboss.org/browse/FORGE-2296
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.15.2.Final
> Reporter: Claus Ibsen
> Assignee: George Gastaldi
> Fix For: 2.15.3.Final
>
>
> When using forge commands in interactive mode, the CLI shows options line by line. Its a bit confusing which are mandatory ,and which are optional.
> Today it shows ? for all options, eg
> {code}
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? componentName (Name of component type to add): [0-179] 165
> ? file (The XML file to use (either Spring or Blueprint)) [META-INF/spring/foo.xml]:
> ? timerName (The name of the timer):
> ***ERROR*** timerName must be specified.
> {code}
> Notice that both file and timerName has a starting ? on the CLI. But both options is required. So its IMHO better to show a * instead to indicate required.
> Here is an example where I am a bit further down in the CLI for the same command
> {code}
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? componentName (Name of component type to add): [0-179] 165
> ? file (The XML file to use (either Spring or Blueprint)) [META-INF/spring/foo.xml]:
> ? timerName (The name of the timer): foo
> ? time (A java.util.Date the first event should be generated. If using the URI the pattern expected is: yyyy-MM-dd HH:mm:ss or yyyy-MM-dd'T'HH:mm:ss.):
> ? period (If greater than 0 generate periodic events every period milliseconds. The default value is 1000.) [1000]: 2000
> ? delay (The number of milliseconds to wait before the first event is generated. Should not be used in conjunction with the time option. The default value is 1000.) [1000]:
> {code}
> The time, period, and delay option is optional. But some of them have a default value which is shown nicely.
> But again this ticket is about changing the ? to a * for the required options.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 6 months
[JBoss JIRA] (FORGE-2296) Forge - Shell in CLI interactive mode, show * for required option and ? for optional
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2296?page=com.atlassian.jira.plugin... ]
Work on FORGE-2296 started by George Gastaldi.
----------------------------------------------
> Forge - Shell in CLI interactive mode, show * for required option and ? for optional
> ------------------------------------------------------------------------------------
>
> Key: FORGE-2296
> URL: https://issues.jboss.org/browse/FORGE-2296
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.15.2.Final
> Reporter: Claus Ibsen
> Assignee: George Gastaldi
>
> When using forge commands in interactive mode, the CLI shows options line by line. Its a bit confusing which are mandatory ,and which are optional.
> Today it shows ? for all options, eg
> {code}
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? componentName (Name of component type to add): [0-179] 165
> ? file (The XML file to use (either Spring or Blueprint)) [META-INF/spring/foo.xml]:
> ? timerName (The name of the timer):
> ***ERROR*** timerName must be specified.
> {code}
> Notice that both file and timerName has a starting ? on the CLI. But both options is required. So its IMHO better to show a * instead to indicate required.
> Here is an example where I am a bit further down in the CLI for the same command
> {code}
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? componentName (Name of component type to add): [0-179] 165
> ? file (The XML file to use (either Spring or Blueprint)) [META-INF/spring/foo.xml]:
> ? timerName (The name of the timer): foo
> ? time (A java.util.Date the first event should be generated. If using the URI the pattern expected is: yyyy-MM-dd HH:mm:ss or yyyy-MM-dd'T'HH:mm:ss.):
> ? period (If greater than 0 generate periodic events every period milliseconds. The default value is 1000.) [1000]: 2000
> ? delay (The number of milliseconds to wait before the first event is generated. Should not be used in conjunction with the time option. The default value is 1000.) [1000]:
> {code}
> The time, period, and delay option is optional. But some of them have a default value which is shown nicely.
> But again this ticket is about changing the ? to a * for the required options.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 6 months
[JBoss JIRA] (FORGE-2296) Forge - Shell in CLI interactive mode, show * for required option and ? for optional
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2296?page=com.atlassian.jira.plugin... ]
George Gastaldi reassigned FORGE-2296:
--------------------------------------
Assignee: George Gastaldi
> Forge - Shell in CLI interactive mode, show * for required option and ? for optional
> ------------------------------------------------------------------------------------
>
> Key: FORGE-2296
> URL: https://issues.jboss.org/browse/FORGE-2296
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.15.2.Final
> Reporter: Claus Ibsen
> Assignee: George Gastaldi
>
> When using forge commands in interactive mode, the CLI shows options line by line. Its a bit confusing which are mandatory ,and which are optional.
> Today it shows ? for all options, eg
> {code}
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? componentName (Name of component type to add): [0-179] 165
> ? file (The XML file to use (either Spring or Blueprint)) [META-INF/spring/foo.xml]:
> ? timerName (The name of the timer):
> ***ERROR*** timerName must be specified.
> {code}
> Notice that both file and timerName has a starting ? on the CLI. But both options is required. So its IMHO better to show a * instead to indicate required.
> Here is an example where I am a bit further down in the CLI for the same command
> {code}
> Press <ENTER> to confirm, or <CTRL>+C to cancel.
> ? componentName (Name of component type to add): [0-179] 165
> ? file (The XML file to use (either Spring or Blueprint)) [META-INF/spring/foo.xml]:
> ? timerName (The name of the timer): foo
> ? time (A java.util.Date the first event should be generated. If using the URI the pattern expected is: yyyy-MM-dd HH:mm:ss or yyyy-MM-dd'T'HH:mm:ss.):
> ? period (If greater than 0 generate periodic events every period milliseconds. The default value is 1000.) [1000]: 2000
> ? delay (The number of milliseconds to wait before the first event is generated. Should not be used in conjunction with the time option. The default value is 1000.) [1000]:
> {code}
> The time, period, and delay option is optional. But some of them have a default value which is shown nicely.
> But again this ticket is about changing the ? to a * for the required options.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 6 months
[JBoss JIRA] (FORGE-2296) Forge - Shell in CLI interactive mode, show * for required option and ? for optional
by Claus Ibsen (JIRA)
Claus Ibsen created FORGE-2296:
----------------------------------
Summary: Forge - Shell in CLI interactive mode, show * for required option and ? for optional
Key: FORGE-2296
URL: https://issues.jboss.org/browse/FORGE-2296
Project: Forge
Issue Type: Feature Request
Components: UI - Shell
Affects Versions: 2.15.2.Final
Reporter: Claus Ibsen
When using forge commands in interactive mode, the CLI shows options line by line. Its a bit confusing which are mandatory ,and which are optional.
Today it shows ? for all options, eg
{code}
Press <ENTER> to confirm, or <CTRL>+C to cancel.
? componentName (Name of component type to add): [0-179] 165
? file (The XML file to use (either Spring or Blueprint)) [META-INF/spring/foo.xml]:
? timerName (The name of the timer):
***ERROR*** timerName must be specified.
{code}
Notice that both file and timerName has a starting ? on the CLI. But both options is required. So its IMHO better to show a * instead to indicate required.
Here is an example where I am a bit further down in the CLI for the same command
{code}
Press <ENTER> to confirm, or <CTRL>+C to cancel.
? componentName (Name of component type to add): [0-179] 165
? file (The XML file to use (either Spring or Blueprint)) [META-INF/spring/foo.xml]:
? timerName (The name of the timer): foo
? time (A java.util.Date the first event should be generated. If using the URI the pattern expected is: yyyy-MM-dd HH:mm:ss or yyyy-MM-dd'T'HH:mm:ss.):
? period (If greater than 0 generate periodic events every period milliseconds. The default value is 1000.) [1000]: 2000
? delay (The number of milliseconds to wait before the first event is generated. Should not be used in conjunction with the time option. The default value is 1000.) [1000]:
{code}
The time, period, and delay option is optional. But some of them have a default value which is shown nicely.
But again this ticket is about changing the ? to a * for the required options.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 6 months
[JBoss JIRA] (FORGE-2268) allow wizards in the CLI to let the user configure non-required inputs
by Claus Ibsen (JIRA)
[ https://issues.jboss.org/browse/FORGE-2268?page=com.atlassian.jira.plugin... ]
Claus Ibsen commented on FORGE-2268:
------------------------------------
+1
This is badly needed. And IMHO should be something forge provides out of the box, as an easy option on the UIInput element.
Users get really confused in the iterative mode when it "appears to not be interactive" and just auto select.
> allow wizards in the CLI to let the user configure non-required inputs
> ----------------------------------------------------------------------
>
> Key: FORGE-2268
> URL: https://issues.jboss.org/browse/FORGE-2268
> Project: Forge
> Issue Type: Feature Request
> Reporter: James Strachan
>
> we're creating wizards for creating new camel components and endpoints. Pretty much all of these have a large number of possible input properties. However most of them are not required.
> I've hacked a multi-page wizard; the 2nd page adds all the non-required inputs to the builder. The CLI then ignores them all and accepts the default values ;)
> It would be nice if there a way prompt the user with something like...
> {code}
> Would you like to change any of the 12 inputs [Yn]:
> Y
> [1] foo
> [2] bar
> ...
> [12] thingy...
> 2
> enter the value for property bar with default value [123] :
> 456
> property bar set to 456
> Would you like to change any of the 12 inputs [Yn]:
> (repeat until n)
> {code}
> i.e. folks can just hit an extra enter to not bother entering any values, or they can keep hitting 'y' then picking the number of the input to change, then the value and enter
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 6 months
[JBoss JIRA] (FORGE-2295) Upgrade to Furnace 2.15.4.Final
by George Gastaldi (JIRA)
George Gastaldi created FORGE-2295:
--------------------------------------
Summary: Upgrade to Furnace 2.15.4.Final
Key: FORGE-2295
URL: https://issues.jboss.org/browse/FORGE-2295
Project: Forge
Issue Type: Component Upgrade
Components: Furnace (Container)
Affects Versions: 2.15.2.Final
Reporter: George Gastaldi
Assignee: George Gastaldi
Fix For: 2.15.3.Final
This is needed to upgrade the Netbeans plugin to a single NBM (See FURNACE-36)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 6 months
[JBoss JIRA] (FURNACE-36) ClassLoader adapter has some unhandled calls to ForgeProxy.getHandler()
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FURNACE-36?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FURNACE-36.
----------------------------------
Resolution: Done
> ClassLoader adapter has some unhandled calls to ForgeProxy.getHandler()
> -----------------------------------------------------------------------
>
> Key: FURNACE-36
> URL: https://issues.jboss.org/browse/FURNACE-36
> Project: Forge: Furnace
> Issue Type: Feature Request
> Components: ClassLoader Adapter
> Affects Versions: 2.15.3.Final
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 2.15.4.Final
>
>
> The following exception is displayed in the Netbeans plugin when runtime and ui NBMs were merged.
> {code}
> java.lang.NullPointerException
> at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport$DefaultMethodHandler.invoke(RuntimeSupport.java:38)
> at org.jboss.forge.netbeans.ui.context.NbUIContext_$$_javassist_e13d8133-0046-41f3-b9a7-9ab73862aac3.getHandler(NbUIContext_$$_javassist_e13d8133-0046-41f3-b9a7-9ab73862aac3.java)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceSingleParameterValue(ClassLoaderAdapterCallback.java:763)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceParameterValues(ClassLoaderAdapterCallback.java:648)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$000(ClassLoaderAdapterCallback.java:37)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:117)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at org.jboss.forge.addon.ui.context.UIContextListener_$$_javassist_adcd450c-b9c4-41af-a35d-0f25acc22d1e.contextInitialized(UIContextListener_$$_javassist_adcd450c-b9c4-41af-a35d-0f25acc22d1e.java)
> {code}
> The solution is to use the {{Proxies.getForgeProxyHandler}} method, as it silently catches any exception in the call to {{ForgeProxy.getHandler}}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 6 months
[JBoss JIRA] (FURNACE-36) ClassLoader adapter has some unhandled calls to ForgeProxy.getHandler()
by George Gastaldi (JIRA)
George Gastaldi created FURNACE-36:
--------------------------------------
Summary: ClassLoader adapter has some unhandled calls to ForgeProxy.getHandler()
Key: FURNACE-36
URL: https://issues.jboss.org/browse/FURNACE-36
Project: Forge: Furnace
Issue Type: Feature Request
Components: ClassLoader Adapter
Affects Versions: 2.15.3.Final
Reporter: George Gastaldi
Assignee: George Gastaldi
Priority: Critical
Fix For: 2.15.4.Final
The following exception is displayed in the Netbeans plugin when runtime and ui NBMs were merged.
{code}
java.lang.NullPointerException
at org.jboss.forge.furnace.proxy.javassist.util.proxy.RuntimeSupport$DefaultMethodHandler.invoke(RuntimeSupport.java:38)
at org.jboss.forge.netbeans.ui.context.NbUIContext_$$_javassist_e13d8133-0046-41f3-b9a7-9ab73862aac3.getHandler(NbUIContext_$$_javassist_e13d8133-0046-41f3-b9a7-9ab73862aac3.java)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceSingleParameterValue(ClassLoaderAdapterCallback.java:763)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceParameterValues(ClassLoaderAdapterCallback.java:648)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$000(ClassLoaderAdapterCallback.java:37)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:117)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
at org.jboss.forge.addon.ui.context.UIContextListener_$$_javassist_adcd450c-b9c4-41af-a35d-0f25acc22d1e.contextInitialized(UIContextListener_$$_javassist_adcd450c-b9c4-41af-a35d-0f25acc22d1e.java)
{code}
The solution is to use the {{Proxies.getForgeProxyHandler}} method, as it silently catches any exception in the call to {{ForgeProxy.getHandler}}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 6 months