[jboss-jira] [JBoss JIRA] (DROOLS-2738) Create a simple, structured or compound data type

[Liz Clayton (JIRA)]

    [ https://issues.jboss.org/browse/DROOLS-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605854#comment-13605854 ] 

Liz Clayton commented on DROOLS-2738:
-------------------------------------

[~karreiro] [~manstis] I ran this by [~tirelli] and he discussed a scaling concern with me - could this handle 20 fields for example? Instead of this approach, we talked about exploring a treegrid-table option. PatternFly has a design that we might be able to leverage: http://www.patternfly.org/pattern-library/widgets/#treegrid-table. The concept being, as [~tirelli] explained it to me, that "1 field per line, where first column is name, second column is type... we can do second column for the "simple/custom" type combobox, and third column for the actual type." If that sounds conceptually do-able to you, you could reach out to [~srambach] for CSS/HTML implementation info for that widget. 


> Create a simple, structured or compound data type
> -------------------------------------------------
>
>                 Key: DROOLS-2738
>                 URL: https://issues.jboss.org/browse/DROOLS-2738
>             Project: Drools
>          Issue Type: Sub-task
>            Reporter: Liz Clayton
>            Assignee: Liz Clayton
>         Attachments: DT-nest-People.pdf
>
>
> We're trying to solve two big issues with this dialog:
>  I) the definition of a simple (basic) data type; and 
> II) the definition of a structured data type.
> * The first one is kind of easy, we just need to provide to the user an input and a select, in order to capture the name and the type of a simple data type. 
> * The second problem is a little bit more difficult. Because the user needs to be able to define complex data types, with nested structures. For example, the user can create a data type called Person with 3 nested fields (they are simple data types) Additionally, a structured data type can have other complex nested data types.
> * Requirement to address situations where we're going to have many levels of nesting and many fields. The user should be able to: a) navigate between levels; b) expand/collapse nested types; c) create complex data structures easily.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)