[
https://issues.jboss.org/browse/DROOLS-3565?page=com.atlassian.jira.plugi...
]
Michael Anstis commented on DROOLS-3565:
----------------------------------------
[~uxdlc] I think, at best, all we can commit to now is that it could be plausible to
re-use the Form Modeller palette code.
We would not want to have a dependency in DMN on Form Modeller so unless their existing
code is eminently re-usable we may not be able to re-use it without some effort in
refactoring. Also, we could only plausibly re-use the palette part and not the drag and
drop from palette to the editor as Stunner and Form Modeller use different technologies:
Form Modeller is all HTML whereas Stunner is part HTML, part Canvas, part Frankenstein!
When we get to implement "import" we'd be able to make a better judgement
call as to what we could re-use (we can obviously make DMN's component palette look
like anything we choose... so we could _borrow_ some HTML from Form Modeller for the
palette's appearance.. but this is not re-use as you ask; but duplication).
DMN: Navigator panel UX updates
-------------------------------
Key: DROOLS-3565
URL:
https://issues.jboss.org/browse/DROOLS-3565
Project: Drools
Issue Type: Task
Components: DMN Editor
Reporter: Liz Clayton
Assignee: Liz Clayton
Priority: Major
Labels: drools-tools
Attachments: Screen Shot 2019-01-28 at 1.38.21 PM.png, Screen Shot 2019-01-28 at
2.35.00 PM.png
As a user I want to be able to be able to view and use imported nodes and decision logic
in the diagram that I am authoring.
Based on card view design (see linked jira), detail new Navigator elements required to
support this workflow including:
- Import components panel: Filter components by BKMs, decisions..., badge count
- Graph panel with checkbox option to view map.
- Single scrolling navigator.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)