[JBoss JIRA] (DROOLS-3652) DMN popover - Enter to apply
by Daniel José dos Santos (Jira)
[ https://issues.jboss.org/browse/DROOLS-3652?page=com.atlassian.jira.plugi... ]
Daniel José dos Santos updated DROOLS-3652:
-------------------------------------------
Sprint: 2019 Week 38-40 (from Sep 16)
> DMN popover - Enter to apply
> -----------------------------
>
> Key: DROOLS-3652
> URL: https://issues.jboss.org/browse/DROOLS-3652
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: UX, drools-tools
> Attachments: Screen Shot 2019-02-13 at 1.20.35 PM.png
>
>
> When the user changes the field value (name in this example), it would be nice if hitting ENTER would apply the name, and take the focus highlight off. The other field is being applied dynamically, so the assumption is that this one is as well.
> !Screen Shot 2019-02-13 at 1.20.35 PM.png|thumbnail!
> p.s. this is the pop-over that needs to be updated to support Expression instead of Name.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4056) DMN Editor: Keyboard shortcut functionality on mouse initiated focus.
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4056?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-4056:
-------------------------------------
[~uxdlc] hello, please is this jira about fixing the single "CTRL-S" shortcut or is it about fixing any applicable shortcut one user "hover" data type entry with mouse?
> DMN Editor: Keyboard shortcut functionality on mouse initiated focus.
> ---------------------------------------------------------------------
>
> Key: DROOLS-4056
> URL: https://issues.jboss.org/browse/DROOLS-4056
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: Field, FieldEnablementFeedback, UX, drools-tools
>
> Keyboard shortcut works only when arrow keys are used to focus on the DMN type element. If the user start editing a field with mouse and type "CTRL-S" to save it, the shortcut does not work.
> Note: Team invested CTRL-S, but there was some potential conflict with built in browser controls.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (JGRP-2129) Schema generation fails on JDK9
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2129?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2129:
--------------------------------
OK, thanks,
> Schema generation fails on JDK9
> -------------------------------
>
> Key: JGRP-2129
> URL: https://issues.jboss.org/browse/JGRP-2129
> Project: JGroups
> Issue Type: Task
> Reporter: Radoslav Husar
> Assignee: Bela Ban
> Priority: Minor
> Labels: jdk9
> Fix For: 5.0
>
>
> Not going to be a problem for a while until base is compiled with JDK9 by default, but just in case.
> {noformat}
> main:
> [mkdir] Created dir: /Users/rhusar/git/jgroups/target/schema
> [java] java.lang.ExceptionInInitializerError
> [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:194)
> [java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:771)
> [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:221)
> [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:135)
> [java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:108)
> [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method)
> [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62)
> [java] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:537)
> [java] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
> [java] at org.apache.tools.ant.Target.execute(Target.java:390)
> [java] at org.apache.tools.ant.Target.performTasks(Target.java:411)
> [java] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
> [java] at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
> [java] at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:327)
> [java] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> [java] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> [java] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> [java] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> [java] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> [java] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> [java] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> [java] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> [java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method)
> [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62)
> [java] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:537)
> [java] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [java] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [java] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [java] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> [java] Caused by: java.lang.ExceptionInInitializerError
> [java] at org.jgroups.conf.ClassConfigurator.<clinit>(ClassConfigurator.java:56)
> [java] at org.jgroups.protocols.ASYM_ENCRYPT.<clinit>(ASYM_ENCRYPT.java:55)
> [java] at java.lang.Class.forName0(java.base@9-ea/Native Method)
> [java] at java.lang.Class.forName(java.base@9-ea/Class.java:291)
> [java] at org.jgroups.util.XMLSchemaGenerator.getClasses(XMLSchemaGenerator.java:127)
> [java] at org.jgroups.util.XMLSchemaGenerator.generateProtocolSchema(XMLSchemaGenerator.java:106)
> [java] at org.jgroups.util.XMLSchemaGenerator.main(XMLSchemaGenerator.java:80)
> [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method)
> [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62)
> [java] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:537)
> [java] at org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:217)
> [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:152)
> [java] ... 38 more
> [java] Caused by: java.lang.NullPointerException
> [java] at org.jgroups.conf.ClassConfigurator.init(ClassConfigurator.java:229)
> [java] at org.jgroups.conf.ClassConfigurator.<clinit>(ClassConfigurator.java:53)
> [java] ... 50 more
> [java] Java Result: -1
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-3652) DMN popover - Enter to apply
by Daniel José dos Santos (Jira)
[ https://issues.jboss.org/browse/DROOLS-3652?page=com.atlassian.jira.plugi... ]
Daniel José dos Santos reassigned DROOLS-3652:
----------------------------------------------
Assignee: Daniel José dos Santos (was: Michael Anstis)
> DMN popover - Enter to apply
> -----------------------------
>
> Key: DROOLS-3652
> URL: https://issues.jboss.org/browse/DROOLS-3652
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: UX, drools-tools
> Attachments: Screen Shot 2019-02-13 at 1.20.35 PM.png
>
>
> When the user changes the field value (name in this example), it would be nice if hitting ENTER would apply the name, and take the focus highlight off. The other field is being applied dynamically, so the assumption is that this one is as well.
> !Screen Shot 2019-02-13 at 1.20.35 PM.png|thumbnail!
> p.s. this is the pop-over that needs to be updated to support Expression instead of Name.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4056) DMN Editor: Keyboard shortcut functionality on mouse initiated focus.
by Daniel José dos Santos (Jira)
[ https://issues.jboss.org/browse/DROOLS-4056?page=com.atlassian.jira.plugi... ]
Daniel José dos Santos reassigned DROOLS-4056:
----------------------------------------------
Assignee: Daniel José dos Santos (was: Guilherme Gomes)
> DMN Editor: Keyboard shortcut functionality on mouse initiated focus.
> ---------------------------------------------------------------------
>
> Key: DROOLS-4056
> URL: https://issues.jboss.org/browse/DROOLS-4056
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: Field, FieldEnablementFeedback, UX, drools-tools
>
> Keyboard shortcut works only when arrow keys are used to focus on the DMN type element. If the user start editing a field with mouse and type "CTRL-S" to save it, the shortcut does not work.
> Note: Team invested CTRL-S, but there was some potential conflict with built in browser controls.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (JGRP-2129) Schema generation fails on JDK9
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/JGRP-2129?page=com.atlassian.jira.plugin.... ]
Radoslav Husar closed JGRP-2129.
--------------------------------
Resolution: Out of Date
Must have gotten fixed along the way, I can no longer reproduce the problem. Closing.
> Schema generation fails on JDK9
> -------------------------------
>
> Key: JGRP-2129
> URL: https://issues.jboss.org/browse/JGRP-2129
> Project: JGroups
> Issue Type: Task
> Reporter: Radoslav Husar
> Assignee: Bela Ban
> Priority: Minor
> Labels: jdk9
> Fix For: 5.0
>
>
> Not going to be a problem for a while until base is compiled with JDK9 by default, but just in case.
> {noformat}
> main:
> [mkdir] Created dir: /Users/rhusar/git/jgroups/target/schema
> [java] java.lang.ExceptionInInitializerError
> [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:194)
> [java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:771)
> [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:221)
> [java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:135)
> [java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:108)
> [java] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method)
> [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62)
> [java] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:537)
> [java] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> [java] at org.apache.tools.ant.Task.perform(Task.java:348)
> [java] at org.apache.tools.ant.Target.execute(Target.java:390)
> [java] at org.apache.tools.ant.Target.performTasks(Target.java:411)
> [java] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
> [java] at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
> [java] at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:327)
> [java] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> [java] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> [java] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> [java] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> [java] at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> [java] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> [java] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> [java] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> [java] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> [java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method)
> [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62)
> [java] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:537)
> [java] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [java] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [java] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [java] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> [java] Caused by: java.lang.ExceptionInInitializerError
> [java] at org.jgroups.conf.ClassConfigurator.<clinit>(ClassConfigurator.java:56)
> [java] at org.jgroups.protocols.ASYM_ENCRYPT.<clinit>(ASYM_ENCRYPT.java:55)
> [java] at java.lang.Class.forName0(java.base@9-ea/Native Method)
> [java] at java.lang.Class.forName(java.base@9-ea/Class.java:291)
> [java] at org.jgroups.util.XMLSchemaGenerator.getClasses(XMLSchemaGenerator.java:127)
> [java] at org.jgroups.util.XMLSchemaGenerator.generateProtocolSchema(XMLSchemaGenerator.java:106)
> [java] at org.jgroups.util.XMLSchemaGenerator.main(XMLSchemaGenerator.java:80)
> [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method)
> [java] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62)
> [java] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43)
> [java] at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:537)
> [java] at org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:217)
> [java] at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:152)
> [java] ... 38 more
> [java] Caused by: java.lang.NullPointerException
> [java] at org.jgroups.conf.ClassConfigurator.init(ClassConfigurator.java:229)
> [java] at org.jgroups.conf.ClassConfigurator.<clinit>(ClassConfigurator.java:53)
> [java] ... 50 more
> [java] Java Result: -1
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4518) Implement UX styles for Test Coverage Report
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4518?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-4518:
-------------------------------------
Sprint: 2019 Week 38-40 (from Sep 16)
> Implement UX styles for Test Coverage Report
> --------------------------------------------
>
> Key: DROOLS-4518
> URL: https://issues.jboss.org/browse/DROOLS-4518
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Yeser Amer
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2019-09-10 at 9.35.23 AM.png, Screen Shot 2019-09-10 at 9.37.02 AM.png, Screenshot from 2019-09-10 17-52-00.png, screenshot-1.png
>
>
> The implemented styles for the Test Coverage Report panel do not align with the HTML/CSS provided in jira https://issues.jboss.org/browse/DROOLS-3741.
> The styles used in the current implementation might present usability concerns - the Decision/Scenario list type size is very small and could pose a readability issue. The layout and alignment of the test summary data is difficult to scan, due to the gutter alignment.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4518) Implement UX styles for Test Coverage Report
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4518?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi reassigned DROOLS-4518:
----------------------------------------
Assignee: Gabriele Cardosi (was: Daniele Zonca)
> Implement UX styles for Test Coverage Report
> --------------------------------------------
>
> Key: DROOLS-4518
> URL: https://issues.jboss.org/browse/DROOLS-4518
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2019-09-10 at 9.35.23 AM.png, Screen Shot 2019-09-10 at 9.37.02 AM.png, Screenshot from 2019-09-10 17-52-00.png, screenshot-1.png
>
>
> The implemented styles for the Test Coverage Report panel do not align with the HTML/CSS provided in jira https://issues.jboss.org/browse/DROOLS-3741.
> The styles used in the current implementation might present usability concerns - the Decision/Scenario list type size is very small and could pose a readability issue. The layout and alignment of the test summary data is difficult to scan, due to the gutter alignment.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months