Hello Christian, first of all thanks for the flowers for the data binding architecture. :)
I took a look at your code especially the table controller code and the first question came to my mind is why do you need a store in the controller. Thats a connection we tried to omit at all cost because we could that way use both parts – the controllers and the stores – separate. And why does the store fire change and changeBubble events? Should not the model be updated and therefore the model throw those events? As you sure can see, i did not dig in too deep into your code. Still too impressed by the demo application. ;) I have one last general question. How did you manage that the changes in the table e.g. in a checkbox appear in all other tables at well? Best, Martin Am 19.05.2009 um 21:12 schrieb panyasan: > > Hello, > > I finished a first alpha version of a databinding feature for the two > virtual widgets, tree and table. The code can bind different > instances of > the virtual widgets to each other, so that they all work with the > same data. > For tree, the use is most obvious when you think of a widget that > shows a > filesystem. If you add a folder at one place, all other trees copy the > change immediately, without the need of reloading the data. On the > other > hand, the databinding feature can communicate with a jsonrpc server > through > a data store to pull data and to propagate data changes to all bound > stores. > > Please have a look at the demo here, it has more information and > instructions: > > http://m53s12.vlinux.de/cboulanger/databinding/build/ > > There are still a LOT of bugs, but you get the idea. If you are > interested, > the classes that implement the behavior can be found here: > > https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib/qcl/trunk/frontend/source/class/qcl/databinding/event/ > > and the code of the application is here > > https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib/qcl/trunk/application/databinding/ > > Hope you find this interesting. Of course, a lot of polishind is > needed and > there is no selection support yet - a critical feature to make it > really > useful in the context of Martin's databinding architecture. In any > case, > thanks to Martin for creating a very good design for the > databinding, which > I hope to have followed - even though for virtual widgets, some > concepts of > the current design do not apply well, so I had to improvise a bit. ;-) > > Cheers, > > Christian > > -- > View this message in context: > http://www.nabble.com/Databinding-for-qx.ui.table.Table-and-qx.ui.treevirtual.TreeVirtual---first-alpha-version-tp23622558p23622558.html > Sent from the qooxdoo-devel mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited royalty-free distribution of the report engine > for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
