On 05/05/10 05:41, Derrell Lipman wrote: > > The standard data binding facilities in qooxdoo have not been > incorporated into the Table widget. This is for at least a few > reasons: (1) Table has it's own pseudo- data binding capabilities (in > the name of Remote Table Model), which is much, much, much older than > qooxdoo data binding, and operates very differently from it. (2) Table > is destined to be obsoleted by a grid/table widget based on the > qx.ui.Virtual mechanism. The new one is planned to have data binding > built in from the start. Because a new table is to be created, no one > has spent the time to implement the standard data binding into the > legacy Table widget. >
hi derrell, whenever someone points to a defect of qx.ui.table.Table, this is the the sort of answer they get. however, 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? > 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) best, burak
------------------------------------------------------------------------------
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
