On Wed, May 5, 2010 at 04:27, Burak Arslan <[email protected]>wrote:
> > when i look at the roadmap, i don't see any plans to rewrite the table > widget. (lists, trees and other widgets are there, but not the table) > so does this mean it's not going to happen before 2011, if ever? > @Martin, do you have the new virtual table widget on your radar? Using qx.ui.table.model.Remote as a model (and qx.ui.table.model.Abstract as your guide), it *might* not be too difficult to create an alternate Remote table model based on Martin's data binding components. This would have the obvious advantages of nice interworking with all of the other data binding components. There would be some tricky parts, particularly the mechanism currently used where the Table asks for (a) how many rows are there, and (b) get me rows n-m. thanks for the suggestions, they'll certainly be useful. > > does the model store have a cache, though? (i haven't stumbled upon any > evidence) if so, how do i configure it? (num. objects in a cache, num. > objects in a page, ttl of objects, etc) > Yes, there is a cache in the current implementation. In fact, much of the code is pertaining to handling the cache. Look at qooxdoo/framework/source/class/qx/ui/table/model/Remote.js for details, and at qooxdoo/framework/source/class/qx/ui/table/model/Abstract.js for specifics of what methods you need to implement. Also, looking at Christian's contrib project for implementing data binding with TreeVirtual will likely be enlightening. Cheers, Derrell
------------------------------------------------------------------------------
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
