December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1949) [DMN Editor]: Context Editor: Row heights should be based on content

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1949?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-1949: ------------------------------------- [~manstis] double negative is quite usual in Slovak language, so no problem :) > [DMN Editor]: Context Editor: Row heights should be based on content > -------------------------------------------------------------------- > > Key: DROOLS-1949 > URL: https://issues.jboss.org/browse/DROOLS-1949 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1949) [DMN Editor]: Context Editor: Row heights should be based on content

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1949?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-1949: ---------------------------------------- [~jomarko] Thanks; good catch... I'm not saying there may not be issues but the initial implementation this represented is complete. (I hope the double-negative above makes sense!!) > [DMN Editor]: Context Editor: Row heights should be based on content > -------------------------------------------------------------------- > > Key: DROOLS-1949 > URL: https://issues.jboss.org/browse/DROOLS-1949 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1949) [DMN Editor]: Context Editor: Row heights should be based on content

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1949?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-1949. ------------------------------------ Resolution: Done > [DMN Editor]: Context Editor: Row heights should be based on content > -------------------------------------------------------------------- > > Key: DROOLS-1949 > URL: https://issues.jboss.org/browse/DROOLS-1949 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1949) [DMN Editor]: Context Editor: Row heights should be based on content

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1949?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-1949: ------------------------------------- [~manstis] Hi, please is this still in progress? > [DMN Editor]: Context Editor: Row heights should be based on content > -------------------------------------------------------------------- > > Key: DROOLS-1949 > URL: https://issues.jboss.org/browse/DROOLS-1949 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2130) [DMN Editor] Boxed Expressions: Relations Expression editor

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2130?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2130: -------------------------------- QE Status: VERIFIED (was: ON_QA) > [DMN Editor] Boxed Expressions: Relations Expression editor > ----------------------------------------------------------- > > Key: DROOLS-2130 > URL: https://issues.jboss.org/browse/DROOLS-2130 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3450?page=com.atlassian.jira.plugi... ] Miroslav Novak commented on WFCORE-3450: ---------------------------------------- Another possibly less painful option might be to use *bold* text for attributes but it depends whether Aesh can do it. wdyt? > CLI - avoid required attributes to be hard to see when using tab completion > ---------------------------------------------------------------------------- > > Key: WFCORE-3450 > URL: https://issues.jboss.org/browse/WFCORE-3450 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Miroslav Novak > > This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( > ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier > allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* > call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection > call-timeout connection-ttl max-hops notification-attempts retry-interval > {code} > it's not clear at the first look how many required attributes there are. > Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. > Discussed on https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2164) [DMN Editor] New Expression Columns doesn't respect width of parent column

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2164: ----------------------------------- Summary: [DMN Editor] New Expression Columns doesn't respect width of parent column Key: DROOLS-2164 URL: https://issues.jboss.org/browse/DROOLS-2164 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.5.0.Final Reporter: Jozef Marko Assignee: Michael Anstis New Expression Column doesn't respect the width of the parent column in the context table. It can be seen if the context table contains multiple entries. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3450?page=com.atlassian.jira.plugi... ] Ingo Weiss commented on WFCORE-3450: ------------------------------------ I agree with this matrix. [~jfdenise], what do you think? > CLI - avoid required attributes to be hard to see when using tab completion > ---------------------------------------------------------------------------- > > Key: WFCORE-3450 > URL: https://issues.jboss.org/browse/WFCORE-3450 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Miroslav Novak > > This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( > ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier > allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* > call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection > call-timeout connection-ttl max-hops notification-attempts retry-interval > {code} > it's not clear at the first look how many required attributes there are. > Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. > Discussed on https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3450?page=com.atlassian.jira.plugi... ] Rostislav Svoboda commented on WFCORE-3450: ------------------------------------------- For color case we would need it configurable (+1 to make colors enabled) and cover following scenarios: * terminal supports color + CLI color on * terminal supports color + CLI color off * terminal does not support color + CLI color on * terminal does not support color + CLI color off Windows seems to be the fun platform - cmd + powershell. Some people can be using stuff like http://cmder.net/ > CLI - avoid required attributes to be hard to see when using tab completion > ---------------------------------------------------------------------------- > > Key: WFCORE-3450 > URL: https://issues.jboss.org/browse/WFCORE-3450 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Miroslav Novak > > This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( > ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier > allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* > call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection > call-timeout connection-ttl max-hops notification-attempts retry-interval > {code} > it's not clear at the first look how many required attributes there are. > Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. > Discussed on https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3450?page=com.atlassian.jira.plugi... ] Rostislav Svoboda updated WFCORE-3450: -------------------------------------- Forum Reference: https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc... > CLI - avoid required attributes to be hard to see when using tab completion > ---------------------------------------------------------------------------- > > Key: WFCORE-3450 > URL: https://issues.jboss.org/browse/WFCORE-3450 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Miroslav Novak > > This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( > ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier > allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* > call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection > call-timeout connection-ttl max-hops notification-attempts retry-interval > {code} > it's not clear at the first look how many required attributes there are. > Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. > Discussed on https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017