Christian,
Very nice demo, as always! I have not been following the data binding
threads much so please forgive me now if my questions are obvious. You
mention that data stores can be bound to other data stores, I am going to
infer that this means if one data store changes (say via selecting a new row
in a table) that it can trigger another data store to update and then any
bound controls of that data store would then update? I hope this makes
sense. What I have lots of in my application, are tables that the data in
them is dependent on the selected row of another table. What I do right now
is when the selection changes on any table (because I do not know
relationships at design time) I have to send a command to the server to
re-fetch all queries and then send a bunch of code back to re-populate the
tables. Being able to set this up to happen on it's own would be
outstanding! I am trying to get a few pieces of my current project to QA,
but when I am finished I think I will dive head first into data binding to
see how much easier my life is going to get with it.
Thanks for the excellent demo and for inspiring me to try it out!
Jim
On Tue, May 19, 2009 at 12:12 PM, panyasan <[email protected]> wrote:
>
> 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
