benco wrote: > > About databinding... As Martin mentioned, I wonder if the qx.data.Array > could work with the actual structure... as it potentially slows the > processes. >
I haven't found time to do any test on that, but I wonder... Internally, the qx.data.Array uses a normal native array, on which it operates. except for the event-firing stuff, why would a "big" qx.data.Array be so much slower than a native one? I guess we would need some performance tests that compare the two. benco wrote: > > I thought a bit about that recently. In my opinion, only the selection and > edition processes are important in most case with virtual tables or trees > (in a databinding way)... In fact, The only problem is when the selection > contains all the table datas (ctrl+a). > Selection and editing is one thing, but I am thinking of other use cases: For example, think of a file system explorer (such as the Mac Finder). If you open several of them, you don't want to have to reload the whole data from the server again. Instead, you can clone the existing tree and bind to it to reflect changes. Another use case for me is "databinding over the wire", i.e. I want to be able to update a tree (or table) structure dynamically and incrementally - when the tree changes on the server (because of the changes applied by another user), I want to immediately have the change reflected in the tree on the client (and all trees bound to that tree). That means another step closer to the behavior of "real" applications. benco wrote: > > If all the datas are modified, we just would have to alert the table that > the model (internal standard js array) is updated without reloading a > hudge qx.data.Array. > Unfortunately, I don't think this will work, since you would have to loop through the whole array to find out what exactly has changed. This problem is solved by qx.data.Array.... But we need performance tests which will help us decide the issue. Thanks for your input, Christian -- View this message in context: http://n2.nabble.com/qooxdoo-contrib-cometd-Dialog-and-VirtualData-tp4247446p4249902.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
