[dojo-contributors] TreeGrid enhancement for 1.6 - lazy loading for children rows

Kris Zyp kzyp at dojotoolkit.org
Fri Oct 1 00:06:45 EDT 2010



On 9/30/2010 4:31 PM, Bill Keese wrote:
> Remember that widgets need to be able to interface to any store.  
> This will make it very difficult.   The interface is:
>
> getChildren() may or may not implement queryOptions, so you cannot
> depend on that feature.    Furthermore, there's no way to know if the
> feature exists except by calling getChildren() with start/length and
> checking if the returned array contains "total".  

That's correct, the code would always call getChildren() with the query
options, and if total wasn't available it would check the length.
Basically (results.total || results.length) which doesn't seem too
terrible.
> I'm not sure if there's any way at all to tell if the sort parameter
> works or not?
>
Has there ever been a way to tell if a store doesn't support sort? With
existing data stores, if sorting is implementing, you just don't get
your items sorted. Also, the implementation that is likely to not have
sort implemented is children array approach, but that approach is
designed for order data, the data that most likely should *not* be
sorted. Generally unordered items are favorable to sorting, ordered
items already have an order and shouldn't be sorted. If someone else
wants the complexity of both, they are certainly can implement it, but
we have make the common case as simple as possible.
Kris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.dojotoolkit.org/pipermail/dojo-contributors/attachments/20100930/920dc644/attachment.htm 


More information about the dojo-contributors mailing list