[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type
by Donato Marrazzo (Jira)
[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ]
Donato Marrazzo commented on DROOLS-3784:
-----------------------------------------
[~uxdlc] I'm not convinced that this is a great benefit. If I understood correctly the context menu is accessible via right click that does not change much the visibility of the feature.
Moreover, it does not change the number of click / action to add a nested element:
1. save the structure node
2. add nested element
3. save nested element
4. add nested element
5. save nested element
etc
Semantically, it's even incorrect! Why should I save something that is not complete? The structure can be saved only when it is completed with all nested element.
When I add a new nested element the structure should be saved again!
The logical sequence of action is:
1. create the structure node
2. add the nested element
3. add the nested element
4. (repeat for all nested elements)
5. save the structure node
I believe that in terms of graphical metaphor the structure should start with a "nested placeholder" with a label "add nested element", when the user clicks the placeholder the new element appears and the placehoder shift down. Look at the attached screenshot.
!nested.png|thumbnail!
> Increase the advanced user productivity when he creates a new Data Type
> -----------------------------------------------------------------------
>
> Key: DROOLS-3784
> URL: https://issues.jboss.org/browse/DROOLS-3784
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.18.0.Final
> Reporter: Donato Marrazzo
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: drools-tools
> Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, nested.png, type-selector.png
>
>
> The Data Type editor could be improved in terms of productivity and usability.
> Ideally, the user should be able to create a complex type minimizing the mouse usage.
> 1) Saving the node is an overhead for basic data type (e.g. age: number)
> 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete.
> 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type
by Donato Marrazzo (Jira)
[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ]
Donato Marrazzo updated DROOLS-3784:
------------------------------------
Attachment: nested.png
> Increase the advanced user productivity when he creates a new Data Type
> -----------------------------------------------------------------------
>
> Key: DROOLS-3784
> URL: https://issues.jboss.org/browse/DROOLS-3784
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.18.0.Final
> Reporter: Donato Marrazzo
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: drools-tools
> Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, nested.png, type-selector.png
>
>
> The Data Type editor could be improved in terms of productivity and usability.
> Ideally, the user should be able to create a complex type minimizing the mouse usage.
> 1) Saving the node is an overhead for basic data type (e.g. age: number)
> 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete.
> 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months
[JBoss JIRA] (WFLY-11900) Wildfly 14 + JGroups + Singleton Cluster Not Working
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFLY-11900?page=com.atlassian.jira.plugin... ]
Paul Ferraro commented on WFLY-11900:
-------------------------------------
[~bhavesh.rkharwa] Please attach server logs from both machines so that we can tell what is preventing your clusters from merging.
In general, singleton services are only as reliable as the cluster on which they run. To ensure that you singleton services do not start while your cluster is partitioned (or, in your case, not yet merged), you should build your singleton service such that it requires a quorum of 2.
> Wildfly 14 + JGroups + Singleton Cluster Not Working
> ----------------------------------------------------
>
> Key: WFLY-11900
> URL: https://issues.jboss.org/browse/WFLY-11900
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Bhavesh Kharwa
> Assignee: Paul Ferraro
> Priority: Major
> Fix For: 14.0.0.Final
>
>
> Singleton cluster is not working if starts both servers at same time.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 7 months