Hi Christian, first of all, happy new year to you too. In general i can only say congratulation and thank you for your good work. But now to some notes in detail:
1.) Its quite interesting that you worked on that topic. I toke some time (but not that much as you) to try comet as well. You can see my chat (using qooxdoo and node.js) on github: http://github.com/wittemann/Chat Its not that much code and not working very well but it was a project for me to get to know comet. So I think it could be quite useful for qooxdoo to have some kind of comet support. The cometd is completely new to me so I cant say anything about it. But I will take a look at it. 3.) That sounds really great and thanks for the kudos. :) It's something we have on our agenda for 2010 for sure. Even better that you are already on that topic. Have you ever made some performance tests with huge trees? The advantage of the virtual tree/table is to handle huge sets of data and I don't know if the data array can handle that amount of data very well. You have sure recognized the reorganization of the io namespaces recently. I think we should tackle the whole io layer in the near future and get that back to a good state. So maybe there will be something like a rpc data store (http://bugzilla.qooxdoo.org/show_bug.cgi?id=2993) which you have on your todo. Best, Martin panyasan wrote: > > Hello all, > > I wish everybody a happy new year with lots of qooxdoo goodies! Let's > start off with three updates from qooxdoo-contrib: > > 1) cometd > > I have been testing my cometd contribution enough to be able to release a > 0.1 version of it: > > http://qooxdoo.org/contrib/project/cometd > https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib/cometd/0.1/ > > Unfortunately, I cannot provide a public demo. I would be interested in > general feedback how much interest there is in integrating cometd > technology into qooxdoo. There is much discussion about the "overkill" of > the Bayeux protocol, but then, it is at least a standard and well tested. > > 2) Dialog > > Another contrib that deserves a 0.1 release is the "Dialog" package: > > "The Dialog project provides many often-used widgets required in user > interaction, such as alert, confirm, prompt, and others that simplify > the web developer's daily work." > > https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib/Dialog/0.1/ > > I have a public demo for that: > > http://www.qxtransformer.org/qooxdoo/dialog/build/ > > so you can see for yourself. I am not very good with design and theming, > so the visual appearance of the dialogs leaves much to be desired. > However, they do what they are supposed to do. > > 3) VirtualData > > Finally, another off-spin of the qcl library. There I have written a > couple of controllers, models, and marshallers to allow databinding for > the TreeVirtual and Table, which currently do not support databinding at > all. The problem is that they use native arrays internally to save the > state of the tree or table, and that updates to these arrays cannot be > monitored. > > However, the qcl approach proved to be a dead end so I started anew, by > rewriting the data model of the widgets themselves. (see > http://bugzilla.qooxdoo.org/show_bug.cgi?id=3289) and creating a new > contrib project so that others can join the effort. > > There's a first version in the qooxdoo-contrib repository: > > https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib/VirtualData/trunk/ > > and I have already a public demo: > > http://www.qxtransformer.org/qooxdoo/virtualdata/build/ > > which shows how to VirtualTree widgets are connected by databinding, with > nothing more than a simple > > tree.getDataModel().bind("model",tree2.getDataModel(),"model"); > > (Kudos to Martin, as usual!!) > > Here's the current todo-list: > > [X] Write a jsonrpc data store > [X] Rewrite qx.ui.treevirtual. SimpleTreeDataModel to use > qx.data.Array instead of native array. > [X] Demo for treevirtual > [ ] Rewrite qx.ui.table.model.* to use qx.data.Array instead > of native array. > [ ] Demo for table > [ ] Controllers and marshalers > [ ] Databinding "across the wire": transport qx.data.Array events > through a choice of transports (jsonrpc, cometd, ...) > [ ] Demo for server-backed databinding > > As usual, I am looking for collaborators. I would think that the > "databound" data models should eventually be part of the framework itself, > but first let's put out a solid version in this contrib projects. > > So much for now, I wish you a good start into the working week (and year). > > Cheers, > Christian > -- View this message in context: http://n2.nabble.com/qooxdoo-contrib-cometd-Dialog-and-VirtualData-tp4247446p4248955.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
