Opened 10 years ago

Closed 9 years ago

Last modified 9 years ago

#11168 closed enhancement (fixed)

[cla][patch] Support hierarchical data

Reported by: Jonathan Bond-Caron Owned by: Jared Jurkiewicz
Priority: high Milestone: 1.7
Component: Data Version: 1.5.0b2
Keywords: Cc: Kris Zyp
Blocked By: Blocking:

Description

The data api currently does not support hierarchical data.

This imposes some limitations like for example the dijit.form.Select or dijit.form.ComboBox? can't support <optgroup></optgroup> markup.

See ticket #11167

This proposed patch for discussion would allow for 'hierarchical data stores' and give more flexibility to how widgets can render data.

There are lots of use cases for this, not just <optgroup></optgroup>

Attachments (1)

hierarchical_totalRecords.patch (20.3 KB) - added by Jonathan Bond-Caron 10 years ago.

Download all attachments as: .zip

Change History (7)

Changed 10 years ago by Jonathan Bond-Caron

comment:1 Changed 9 years ago by bill

Cc: Kris Zyp added

I think this will be addressed with the new dojo.data (or whatever we call it) API matching the HTML5 object interface where an item is simple a (JSON-esque) Object, see the dojo contributors thread.

Although that won't be appropriate for deeply hierarchical data like for a Tree control.

comment:2 Changed 9 years ago by Jonathan Bond-Caron

Thanks, one approach could be:

new dijit.form.ComboBox?({store: html5api, schema: metadata});

Where metadata.getParent(item) could be called for find parents for that item...

comment:3 Changed 9 years ago by Jared Jurkiewicz

Milestone: tbdfuture

comment:4 Changed 9 years ago by Kris Zyp

In the new API there is a getChildren() method defined. http://docs.dojocampus.org/dojo/store

Does that help with this?

comment:5 Changed 9 years ago by Kris Zyp

Resolution: fixed
Status: newclosed

I believe the new API has adequate support for hierarchy

comment:6 Changed 9 years ago by bill

Milestone: future1.7
Note: See TracTickets for help on using tickets.