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? best regards, burak ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
