]
Michael Anstis moved GUVNOR-1190 to DROOLS-2047:
------------------------------------------------
Project: Drools (was: Guvnor)
Key: DROOLS-2047 (was: GUVNOR-1190)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Component/s: DSLs Editor
(was: DSL)
Guided Editor: Nested DSL UI Suggestion
---------------------------------------
Key: DROOLS-2047
URL:
https://issues.jboss.org/browse/DROOLS-2047
Project: Drools
Issue Type: Feature Request
Components: DSLs Editor
Reporter: Brad Davis
Assignee: Michael Anstis
Priority: Minor
Attachments: current-fact-entry.jpg, future-nested-condition-entry.jpg
When there is a large set of DSL, with nested statements, the UI for Rules creation
becomes cluttered. I propose that we change the simple List to a expandable table
structure for Fact Assertion.
For Example,
[when]There is a Patient with Cholesterol Readings=$c : Cholesterol()
[when]-With the Gender {gender}=patient.gender=="{gender}"
[when]-With Age Between {lower:[0-9]+} and {upper}=patient.age <= {lower}, patient.age
>= {upper}
[when]-With Cholesterol of {cholesterol} mg/dl or above=mgdl >={cholesterol}
[when]-With Cholesterol of {cholesterol} mg/dl or below=mgdl <={cholesterol}
[when]-With Cholesterol between {lower} mg/dl and {upper} mg/dl=mgdl >={lower},
mgdl<={upper}
This leads to fact entry such as the screenshot attached. As you can imagine, creating
rules with many DSLs would become overwhelming quickly to sort through. I think maybe we
should use a Tree view instead of a list here. This would allow you to drill down to
nested DSL statements. Also, when creating a child of the DSL statement, only the
children DRL statements should be displayed on the screen.
Attached are the current entry, and a mockup of how I would like to see this working in
the future. I think it could simplify and organize the fact creation quite a bit.