[JBoss JIRA] (DROOLS-4654) [DMN Designer] Cues to help users add nodes to the diagram
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-4654?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-4654:
----------------------------------------
[~roger600] Perfectamondo :-)
> [DMN Designer] Cues to help users add nodes to the diagram
> ----------------------------------------------------------
>
> Key: DROOLS-4654
> URL: https://issues.jboss.org/browse/DROOLS-4654
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: Field, Stunner, UX, UX-Field, UXTeam, drools-tools
> Attachments: mouse-pointer.svg, screenshot-1.png
>
>
> Users are unable to add nodes the process diagram. In both the legacy editor and in Stunner, they do not understand that you need to drag the components onto the canvas. Some users click and then click on the canvas, while others can't even find where, for example, the script task is.
> *_Acceptance criteria_*
> See https://issues.jboss.org/browse/RHPAM-2318 for acceptance criteria.
> The empty state text should state "diagram" and not "business process".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4654) [DMN Designer] Cues to help users add nodes to the diagram
by Roger Martinez (Jira)
[ https://issues.jboss.org/browse/DROOLS-4654?page=com.atlassian.jira.plugi... ]
Roger Martinez commented on DROOLS-4654:
----------------------------------------
FYI [~kgaevski] [~alessandrolt] ^^
> [DMN Designer] Cues to help users add nodes to the diagram
> ----------------------------------------------------------
>
> Key: DROOLS-4654
> URL: https://issues.jboss.org/browse/DROOLS-4654
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: Field, Stunner, UX, UX-Field, UXTeam, drools-tools
> Attachments: mouse-pointer.svg, screenshot-1.png
>
>
> Users are unable to add nodes the process diagram. In both the legacy editor and in Stunner, they do not understand that you need to drag the components onto the canvas. Some users click and then click on the canvas, while others can't even find where, for example, the script task is.
> *_Acceptance criteria_*
> See https://issues.jboss.org/browse/RHPAM-2318 for acceptance criteria.
> The empty state text should state "diagram" and not "business process".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4654) [DMN Designer] Cues to help users add nodes to the diagram
by Roger Martinez (Jira)
[ https://issues.jboss.org/browse/DROOLS-4654?page=com.atlassian.jira.plugi... ]
Roger Martinez edited comment on DROOLS-4654 at 11/11/19 4:16 PM:
------------------------------------------------------------------
Yeah [~manstis] [~bdellasc] [~josephblt]
I also think so, we should use same empty screen and toolbox behavior (on first use) in all domains - BPMN, DM and DMN.
I also think that only difference on the text literals, between domains, it's only about the "process" word/term, so I would replace "process" for:
* DMN -> "diagram"
* CM -> "case"
Does that makes sense for you guys? Are we all ok with this?
[~josephblt] Also you'll have to ensure, in all domains, once creating a new process/case/diagram it appears empty. I think you already have it for BPMN, but please ensure also DMN and CM are "empty" once creating them, otherwise the "empty screen" will be not initially presented
Thx!
was (Author: roger600):
Yeah [~manstis] [~bdellasc] [~josephblt]
I also think so, we should use same empty screen and toolbox behavior (on first use) in all domains - BPMN, DM and DMN.
I also think that only difference on the text literals, between domains, it's only about the "process" word/term, so I would replace "process" for:
* DMN -> "diagram"
* CM -> "case"
Does that makes sense for you guys? Are we all ok with this?
Thx!
> [DMN Designer] Cues to help users add nodes to the diagram
> ----------------------------------------------------------
>
> Key: DROOLS-4654
> URL: https://issues.jboss.org/browse/DROOLS-4654
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: Field, Stunner, UX, UX-Field, UXTeam, drools-tools
> Attachments: mouse-pointer.svg, screenshot-1.png
>
>
> Users are unable to add nodes the process diagram. In both the legacy editor and in Stunner, they do not understand that you need to drag the components onto the canvas. Some users click and then click on the canvas, while others can't even find where, for example, the script task is.
> *_Acceptance criteria_*
> See https://issues.jboss.org/browse/RHPAM-2318 for acceptance criteria.
> The empty state text should state "diagram" and not "business process".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4654) [DMN Designer] Cues to help users add nodes to the diagram
by Roger Martinez (Jira)
[ https://issues.jboss.org/browse/DROOLS-4654?page=com.atlassian.jira.plugi... ]
Roger Martinez commented on DROOLS-4654:
----------------------------------------
Yeah [~manstis] [~bdellasc] [~josephblt]
I also think so, we should use same empty screen and toolbox behavior (on first use) in all domains - BPMN, DM and DMN.
I also think that only difference on the text literals, between domains, it's only about the "process" word/term, so I would replace "process" for:
* DMN -> "diagram"
* CM -> "case"
Does that makes sense for you guys? Are we all ok with this?
Thx!
> [DMN Designer] Cues to help users add nodes to the diagram
> ----------------------------------------------------------
>
> Key: DROOLS-4654
> URL: https://issues.jboss.org/browse/DROOLS-4654
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: Field, Stunner, UX, UX-Field, UXTeam, drools-tools
> Attachments: mouse-pointer.svg, screenshot-1.png
>
>
> Users are unable to add nodes the process diagram. In both the legacy editor and in Stunner, they do not understand that you need to drag the components onto the canvas. Some users click and then click on the canvas, while others can't even find where, for example, the script task is.
> *_Acceptance criteria_*
> See https://issues.jboss.org/browse/RHPAM-2318 for acceptance criteria.
> The empty state text should state "diagram" and not "business process".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-12775) Deconstruct wildfly-clustering-common
by Paul Ferraro (Jira)
Paul Ferraro created WFLY-12775:
-----------------------------------
Summary: Deconstruct wildfly-clustering-common
Key: WFLY-12775
URL: https://issues.jboss.org/browse/WFLY-12775
Project: WildFly
Issue Type: Task
Components: Clustering
Affects Versions: 18.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
wildfly-clustering-common began as a module to house code common to clustering-related subsystem modules (e.g. infinispan, jgroups, singleton, mod_cluster, etc). While this module is currently still a dumping ground of sorts, the majority of the code contained within makes up a framework for quickly building and evolving subsystems, with minimal boilerplate code, including:
* Simplified model/operation/attribute/metric registration
* Interfaces for enumerating schema and management model versions, used for parameterizing parsers and transfomers
* Generic add/remove operation handlers with a clean distinction between runtime behavior and model behavior.
* Mechanisms for easily renaming/relocating management attributes
* Abstractions for using capabilities
* Generic Resource decorator augmented to support additional runtime children.
* Abstractions for correctly implementing runtime operations and metrics using values from an MSC service
* Abstractions for complex transformers
On top of subsystem development abstractions, this module also contains:
* Abstractions for contextual execution
** Move to separate module
* Service configurator for JNDI bindings
** Move to separate module
* Helper methods for obtaining optional model values
** These are largely redundant now
* Common Function/Predicate/Consumer implementations
** These can likely be replaced with implementations from wildfly-common or guava
Once cleaned up, and excess dependencies eliminated, we can rename it to something more descriptive (e.g. wildfly-subsystem).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4654) [DMN Designer] Cues to help users add nodes to the diagram
by Brian Dellascio (Jira)
[ https://issues.jboss.org/browse/DROOLS-4654?page=com.atlassian.jira.plugi... ]
Brian Dellascio commented on DROOLS-4654:
-----------------------------------------
[~josephblt], If what you mentioned above is what's being used in the BPMN tooltips and the functionality is the same, then we should use the same tooltips in DMN. Thanks for checking in!
CC [~manstis]
> [DMN Designer] Cues to help users add nodes to the diagram
> ----------------------------------------------------------
>
> Key: DROOLS-4654
> URL: https://issues.jboss.org/browse/DROOLS-4654
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: Field, Stunner, UX, UX-Field, UXTeam, drools-tools
> Attachments: mouse-pointer.svg, screenshot-1.png
>
>
> Users are unable to add nodes the process diagram. In both the legacy editor and in Stunner, they do not understand that you need to drag the components onto the canvas. Some users click and then click on the canvas, while others can't even find where, for example, the script task is.
> *_Acceptance criteria_*
> See https://issues.jboss.org/browse/RHPAM-2318 for acceptance criteria.
> The empty state text should state "diagram" and not "business process".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4654) [DMN Designer] Cues to help users add nodes to the diagram
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-4654?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-4654:
----------------------------------------
Hi [~josephblt] IMO, for consistency, do exactly the same as BPMN (and presumably CM) : "To add a new (name of node), click or drag the icon"
The only change for DMN (to that being done for BPMN) is the _empty state_ text that should make reference to "diagram" as opposed to "business process".
> [DMN Designer] Cues to help users add nodes to the diagram
> ----------------------------------------------------------
>
> Key: DROOLS-4654
> URL: https://issues.jboss.org/browse/DROOLS-4654
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: Field, Stunner, UX, UX-Field, UXTeam, drools-tools
> Attachments: mouse-pointer.svg, screenshot-1.png
>
>
> Users are unable to add nodes the process diagram. In both the legacy editor and in Stunner, they do not understand that you need to drag the components onto the canvas. Some users click and then click on the canvas, while others can't even find where, for example, the script task is.
> *_Acceptance criteria_*
> See https://issues.jboss.org/browse/RHPAM-2318 for acceptance criteria.
> The empty state text should state "diagram" and not "business process".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months