On Tue, May 4, 2010 at 17:43, Burak Arslan <[email protected]>wrote:
> hi, > > i think separating the object cache of the remote table model would be a > nice feature that will relieve the load on the data source and improve > memory usage. > > in our case, we sometimes have to show the same data in two places, or > at different times, or inside different widgets, etc. > > we also sometimes have to use the remote data in other places. it's > difficult because it may be available in multiple places. it's also > awkward, as we often have to query a table widget instead of just > querying a key-value store. > > so i think it'd be a valuable addition to qooxdoo's data management > abilities. > > once we have this, making modifications to remote data should also be > easier, as it'll go through one source. > > so, 1) do you like the idea? 2) would the data binding framework help me > doing this? if yes, any pointers? > 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. 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. If you'd like to implement something to act as a remote model for Table that's based on standard qooxdoo data binding, it would probably be quite appreciated by a number of users. Cheers, Derrell
------------------------------------------------------------------------------
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
