[JBoss JIRA] (DROOLS-3048) [DMN Designer] CellEditorControl needs to issue a new instance per use
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-3048?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-3048:
-----------------------------------
Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 50-52 (from Dec 9))
> [DMN Designer] CellEditorControl needs to issue a new instance per use
> ----------------------------------------------------------------------
>
> Key: DROOLS-3048
> URL: https://issues.redhat.com/browse/DROOLS-3048
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> A {{Popover}} used to edit a cell or column header (or any other DOM-based editor for that matter) disappears following a change in the widget that causes a {{Layer.draw()}} if the grid is sufficiently wide that there is a column not visible on screen.
> All cells/columns that use {{CellEditorControls}} (containing, for example, the {{Popover}}) share a single instance from {{CellEditorControl}} and hence although the User makes a change in a visible column the invisible column (scrolled off screen) has its DOM resources destroyed that is the same instance as that for the visible column.
> See https://github.com/kiegroup/appformer/blob/master/uberfire-extensions/ube.... If a column is not in the _body_ or _floating_ columns collection its DOM resources are destroyed.
> I probably need to ensure different instances of {{CellEditorControl}} are created for each column/cell where we currently share the same instance. Also check for destruction of DOM elements in {{Document}} when grids/columns etc are destroyed.
> h3. Acceptance criteria
> # Create a DMN model
> # Add a Decision
> # Set its expression to a Decision Table
> # Add multiple Input and Output columns so that the table is wider than the visible screen space (i.e. some columns are not rendered)
> # Click on the header of a visible column
> # The Name/Data-type popup should appear
> # Repeat for expression type of Relation
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (DROOLS-2845) Extend the existing verifier to support DMN tables
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-2845?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-2845:
-----------------------------------
Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9))
> Extend the existing verifier to support DMN tables
> --------------------------------------------------
>
> Key: DROOLS-2845
> URL: https://issues.redhat.com/browse/DROOLS-2845
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor, verifier
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Optional
> Labels: UX, drools-tools, verifier
>
> h1. Goal
> Reuse the V&V created for Guided Decision Tables on the DMN tables.
> h1. Workload divided to steps
> I propose the work goes in the following steps. After each step I should be able to merge into master.
> Steps:
> # Move Verifier core to kie-wb-common
> # Move V&V reporting UI to kie-wb-common
> # Make the web worker connector reusable for different V&V types
> # -Make a servlet module for DMN that allows the download of the Web Worker.-
> # Create an adapter for DMN tables
> # Add support for ranges ( these are given in DMN so no need to use JSR303 )
> # Duplicate i18n of the V&V for DMN or unify the reports so that the terms make sense
> The workload has changed. Now the goal is to reuse the DRL V&V codes in the existing DMN Codes. This means most of the work done for this ticket has no effect and the goal is to adjust to existing DMN V&V reporting, not the other way around.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (DROOLS-4641) Running the Traffic Violation tutorial closing DMN editor Zoom toolbar persisted
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4641?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4641:
-----------------------------------
Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 50-52 (from Dec 9))
> Running the Traffic Violation tutorial closing DMN editor Zoom toolbar persisted
> --------------------------------------------------------------------------------
>
> Key: DROOLS-4641
> URL: https://issues.redhat.com/browse/DROOLS-4641
> Project: Drools
> Issue Type: Bug
> Components: Stunner
> Reporter: Matteo Mortari
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: image-2019-10-11-11-16-50-339.png
>
>
> As per title. Following the Traffic Violation tutorial. Closing the DMN editor. the Zoom bar persist on screen as per screenshot.
> !image-2019-10-11-11-16-50-339.png|thumbnail!
> Not sure this is the correct JIRA component, please move this JIRA as necessary
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years