[JBoss JIRA] (DROOLS-2762) [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table)
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2762?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro commented on DROOLS-2762:
--------------------------------------------
[~jomarko] currently we don't support undo/redo operations inside of the dialog (we can discuss if this makes sense for a dialog and estimate separately).
> [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2762
> URL: https://issues.jboss.org/browse/DROOLS-2762
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: DROOLS-2762.png
>
>
> The "Add component" creates new lines (in the treegrid-table) representing nested fields (in ItemDefinition):
> - This component must be disabled (or hidden) when an existing/primitive data type is selected.
> h3. Acceptance test
> - User not able to add and save lines that are filled just partially
> - Check added rows after reopening
> - Check undo redo commands
> - The "Add row" button must always appear to the user (e.q. a lot of item definitions present)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2762) [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table)
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2762?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-2762:
---------------------------------------
Description:
The "Add component" creates new lines (in the treegrid-table) representing nested fields (in ItemDefinition):
- This component must be disabled (or hidden) when an existing/primitive data type is selected.
h3. Acceptance test
- User not able to add and save lines that are filled just partially
- Check added rows after reopening
- The "Add row" button must always appear to the user (e.q. a lot of item definitions present)
was:
The "Add component" creates new lines (in the treegrid-table) representing nested fields (in ItemDefinition):
- This component must be disabled (or hidden) when an existing/primitive data type is selected.
h3. Acceptance test
- User not able to add and save lines that are filled just partially
- Check added rows after reopening
- Check undo redo commands
- The "Add row" button must always appear to the user (e.q. a lot of item definitions present)
> [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2762
> URL: https://issues.jboss.org/browse/DROOLS-2762
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: DROOLS-2762.png
>
>
> The "Add component" creates new lines (in the treegrid-table) representing nested fields (in ItemDefinition):
> - This component must be disabled (or hidden) when an existing/primitive data type is selected.
> h3. Acceptance test
> - User not able to add and save lines that are filled just partially
> - Check added rows after reopening
> - The "Add row" button must always appear to the user (e.q. a lot of item definitions present)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2881) [DMN Designer] Data type dialog - "Destroy" action in the list view
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2881?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro commented on DROOLS-2881:
--------------------------------------------
[~jomarko] currently we don't support undo/redo operations inside of the dialog (we can discuss if this makes sense for a dialog and estimate separately).
> [DMN Designer] Data type dialog - "Destroy" action in the list view
> -------------------------------------------------------------------
>
> Key: DROOLS-2881
> URL: https://issues.jboss.org/browse/DROOLS-2881
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: DROOLS-2881.png
>
>
> - This task refers to the icon, and to the action of removing the data type from the DMN file.
> h3. Acceptance test
> - Remove item referred from other item definition
> - Check removing after reopening
> - Check undo/redo command
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2881) [DMN Designer] Data type dialog - "Destroy" action in the list view
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2881?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-2881:
---------------------------------------
Description:
- This task refers to the icon, and to the action of removing the data type from the DMN file.
h3. Acceptance test
- Remove item referred from other item definition
- Check removing after reopening
was:
- This task refers to the icon, and to the action of removing the data type from the DMN file.
h3. Acceptance test
- Remove item referred from other item definition
- Check removing after reopening
- Check undo/redo command
> [DMN Designer] Data type dialog - "Destroy" action in the list view
> -------------------------------------------------------------------
>
> Key: DROOLS-2881
> URL: https://issues.jboss.org/browse/DROOLS-2881
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: DROOLS-2881.png
>
>
> - This task refers to the icon, and to the action of removing the data type from the DMN file.
> h3. Acceptance test
> - Remove item referred from other item definition
> - Check removing after reopening
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2968) Improve stateless ksession throughput performance
by Mark Proctor (JIRA)
Mark Proctor created DROOLS-2968:
------------------------------------
Summary: Improve stateless ksession throughput performance
Key: DROOLS-2968
URL: https://issues.jboss.org/browse/DROOLS-2968
Project: Drools
Issue Type: Feature Request
Reporter: Mark Proctor
Assignee: Mario Fusco
Stateless access has become too heavy. We should look at streamlining the api, to avoid unnecessary work, and unnecessary (on demand) object creation. For example we know if rules need timers, avoid the timer creation if not necessary.
Also we should look at (with evaluation first) to determine if a Three local cache of ksessions, with reset, will help improve GC impact.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2967) Immutable callback model as apposed to mutable listeners
by Mark Proctor (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2967?page=com.atlassian.jira.plugi... ]
Mark Proctor commented on DROOLS-2967:
--------------------------------------
We should transition KIE to using single method callbacks, instead of lists of listeners.
If the user wishes to use a list os listeners they can use an adapter. In effect this would be like moving the current EventSupport class as an external library for end users.
All callbacks must be set a instantiation time and are not mutable. If the users wishes to mutate, or have a list of listeners, they can do that in their adapter.
This way we push thread handling out to the user, and see Kie work "bare metal". It will remove complicated code, that assumes the most pessimistic use cases for multi-threading - especially as it's rate those listeners change, so why incur the cost?
Further a callback approach passes all objects as arguments, instead of create an Event wrapper object. For light weight stream analysis, we want to minimise he GC impact - so every object less, helps. Again if the user wants a listener model, with Event object, this can be done in the adapter.
We can provide base adapters for the users, they can also write their own.
> Immutable callback model as apposed to mutable listeners
> --------------------------------------------------------
>
> Key: DROOLS-2967
> URL: https://issues.jboss.org/browse/DROOLS-2967
> Project: Drools
> Issue Type: Feature Request
> Reporter: Mark Proctor
> Assignee: Mario Fusco
> Labels: MDP_BRAINFARTS
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months