Re: [qooxdoo-devel] WebSocket implementation
I've used Microsoft SignalR for real-time web messaging before. It has a javascript client library but requires jQuery. It would be nice if there is a qooxdoo equivalent though so we can throw away the jQuery requirement. -- View this message in context: http://qooxdoo.678.n2.nabble.com/WebSocket-implementation-tp7586370p7587028.html Sent from the qooxdoo mailing list archive at Nabble.com. -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] WebSocket implementation
So what happened to this? Does it become a contrib ? where it gone ? I didn't see websocket qooxdoo source and no contribs either. I really believe qooxdoo need websocket functionality. On Mon, Dec 29, 2014 at 8:21 PM, halcwb wrote: > Phyo Arkar wrote >> Check the development process of Atom.io and how lively and thriving it is >> , although it is Coffeescript. >> Also check rethinkdb's Github. >> If qooxdoo is easy to contribute and development process is open , it will >> grow a lot faster , and will have alot of users. >> >> People can contribute at Atom.io and Rethinkdb easier due the fact they >> use >> Github to its max, and its fun to do so . Currently I do not like BugZilla >> for bug report and Code repistory for Github approach. > > I agree with the above as well. Coming from ExtJs, at least you have a > transparent and open bug report system. But I would like more consistency. > > > > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/WebSocket-implementation-tp7586370p7586547.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > -- > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] WebSocket implementation
Phyo Arkar wrote > Check the development process of Atom.io and how lively and thriving it is > , although it is Coffeescript. > Also check rethinkdb's Github. > If qooxdoo is easy to contribute and development process is open , it will > grow a lot faster , and will have alot of users. > > People can contribute at Atom.io and Rethinkdb easier due the fact they > use > Github to its max, and its fun to do so . Currently I do not like BugZilla > for bug report and Code repistory for Github approach. I agree with the above as well. Coming from ExtJs, at least you have a transparent and open bug report system. But I would like more consistency. -- View this message in context: http://qooxdoo.678.n2.nabble.com/WebSocket-implementation-tp7586370p7586547.html Sent from the qooxdoo mailing list archive at Nabble.com. -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] WebSocket implementation
On Thu, 27 Nov 2014, Phyo Arkar wrote: > Back on topic, Thanks a lot stefan , i really believe Websocket need to be > inside Qooxdoo . As installing contributions in qooxdoo need a quite abit > of work. Well ... compared to the actual implementation this is probably a small percentage of the effort. Especially once you have done it once. And using is simple enough, just adding a line to config.json > We are also trying to port SockJS to qooxdoo and its quite a bit of work to > make it qooxdoo-ish . But you get all the benefits you probably like from it being qooxdooish ... Cheers, Fritz -- Oetiker+Partner AG tel: +41 62 775 9903 (direct) Fritz Zaucker+41 62 775 9900 (switch board) Aarweg 15+41 79 675 0630 (mobile) CH-4600 Olten fax: +41 62 775 9905 Schweiz web: www.oetiker.ch -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] WebSocket implementation
Check the development process of Atom.io and how lively and thriving it is , although it is Coffeescript. Also check rethinkdb's Github. If qooxdoo is easy to contribute and development process is open , it will grow a lot faster , and will have alot of users. People can contribute at Atom.io and Rethinkdb easier due the fact they use Github to its max, and its fun to do so . Currently I do not like BugZilla for bug report and Code repistory for Github approach. Back on topic, Thanks a lot stefan , i really believe Websocket need to be inside Qooxdoo . As installing contributions in qooxdoo need a quite abit of work. We are also trying to port SockJS to qooxdoo and its quite a bit of work to make it qooxdoo-ish . On Thu, Nov 13, 2014 at 3:12 PM, John Spackman wrote: > I agree with Stefan; opening up the development process would be good for > the community and good for Qoxodoo. > > John > > > On 13 Nov 2014, at 08:27, [email protected] wrote: > > > > Hi Fritz! > > > >> I also understand the argument about core functionality. But putting it > >> there only helps if 1&1 has the necessary ressources to maintain it (or > at > >> least to make sure updates/fixes are checked and integrated in a timely > >> manner). > > > > It is so true and therefore maybe 1&1 should look for a different way of > working like for example the Fedora team, if they really want a vivid > community. > > By looking at adding functionality, as in this case separated from other > core functionality, as a part of the project, it might be more time > efficient to follow up on maintainers instead of doing all themselves... > > > > Stefan > > > >> Cheers, > >> Fritz > >> > >> On Thu, 13 Nov 2014, [email protected] wrote: > >> > >>> Hi Martin, > >>> > >>> It is easy to keep it as a contribution if that is what you want. > >>> We chose an enhancement bug as Script/Xhr/Jsonp communication are core > functionality and we believe websocket should be too. > >>> We also used the qx.io namespace of the same reason. > >>> We believed it might help you > >>> > >>> ...but you are right regarding updates... > >>> > >>> so we switch it to a contribution with the above namespace. > >>> > >>> Stefan > >>> > Hallo Stefan, > first of all, thank you very much. I didn?t have time to check out > any details but one questions came to my mind right away. Why did you > decide to use a pull request instead of a contribution? This topic seems to > be so huge and self contained, it could be easily a contribution as well > where you would keep the control over your code and don?t have to file a > pull request for every other enhancement / bugfix. > Regards, > Martin > > > Am 12.11.2014 um 15:47 schrieb [email protected]: > > > > We have sent a pull request to the qooxdoo. > > > > As WebSockets have not been implemented the qooxdoo way with basic, > fallback, reconnection, pool, cache, data binding etc, we decided to start > it. > > > > Any suggestions on it would be appreciated. > > > > Stefan > > > > > -- > > Comprehensive Server Monitoring with Site24x7. > > Monitor 10 servers for $9/Month. > > Get alerted through email, SMS, voice calls or mobile push > notifications. > > Take corrective actions from your mobile device. > > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > > ___ > > qooxdoo-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push > notifications. > Take corrective actions from your mobile device. > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > >>> > >>> > >>> > >>> > -- > >>> Comprehensive Server Monitoring with Site24x7. > >>> Monitor 10 servers for $9/Month. > >>> Get alerted through email, SMS, voice calls or mobile push > notifications. > >>> Take corrective actions from your mobile device. > >>> > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > >>> ___ > >>> qooxdoo-devel mailing list > >>> [email protected] > >>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > >> > >> -- > >> Oetiker+Partner AG tel: +41 62 775 9903 (direct) > >>
Re: [qooxdoo-devel] WebSocket implementation
I agree with Stefan; opening up the development process would be good for the community and good for Qoxodoo. John > On 13 Nov 2014, at 08:27, [email protected] wrote: > > Hi Fritz! > >> I also understand the argument about core functionality. But putting it >> there only helps if 1&1 has the necessary ressources to maintain it (or at >> least to make sure updates/fixes are checked and integrated in a timely >> manner). > > It is so true and therefore maybe 1&1 should look for a different way of > working like for example the Fedora team, if they really want a vivid > community. > By looking at adding functionality, as in this case separated from other core > functionality, as a part of the project, it might be more time efficient to > follow up on maintainers instead of doing all themselves... > > Stefan > >> Cheers, >> Fritz >> >> On Thu, 13 Nov 2014, [email protected] wrote: >> >>> Hi Martin, >>> >>> It is easy to keep it as a contribution if that is what you want. >>> We chose an enhancement bug as Script/Xhr/Jsonp communication are core >>> functionality and we believe websocket should be too. >>> We also used the qx.io namespace of the same reason. >>> We believed it might help you >>> >>> ...but you are right regarding updates... >>> >>> so we switch it to a contribution with the above namespace. >>> >>> Stefan >>> Hallo Stefan, first of all, thank you very much. I didn?t have time to check out any details but one questions came to my mind right away. Why did you decide to use a pull request instead of a contribution? This topic seems to be so huge and self contained, it could be easily a contribution as well where you would keep the control over your code and don?t have to file a pull request for every other enhancement / bugfix. Regards, Martin > Am 12.11.2014 um 15:47 schrieb [email protected]: > > We have sent a pull request to the qooxdoo. > > As WebSockets have not been implemented the qooxdoo way with basic, > fallback, reconnection, pool, cache, data binding etc, we decided to > start it. > > Any suggestions on it would be appreciated. > > Stefan > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >>> >>> >>> >>> -- >>> Comprehensive Server Monitoring with Site24x7. >>> Monitor 10 servers for $9/Month. >>> Get alerted through email, SMS, voice calls or mobile push notifications. >>> Take corrective actions from your mobile device. >>> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >>> ___ >>> qooxdoo-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> >> -- >> Oetiker+Partner AG tel: +41 62 775 9903 (direct) >> Fritz Zaucker+41 62 775 9900 (switch board) >> Aarweg 15+41 79 675 0630 (mobile) >> CH-4600 Olten fax: +41 62 775 9905 >> Schweiz web: www.oetiker.ch >> >> -- >> Comprehensive Server Monitoring with Site24x7. >> Monitor 10 servers for $9/Month. >> Get alerted through email, SMS, voice calls or mobile push notifications. >> Take corrective actions from your mobile device. >> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >> ___ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > > -- > Comprehensive Ser
Re: [qooxdoo-devel] WebSocket implementation
Hi Fritz! > I also understand the argument about core functionality. But putting it > there only helps if 1&1 has the necessary ressources to maintain it (or at > least to make sure updates/fixes are checked and integrated in a timely > manner). It is so true and therefore maybe 1&1 should look for a different way of working like for example the Fedora team, if they really want a vivid community. By looking at adding functionality, as in this case separated from other core functionality, as a part of the project, it might be more time efficient to follow up on maintainers instead of doing all themselves... Stefan > Cheers, > Fritz > > On Thu, 13 Nov 2014, [email protected] wrote: > >> Hi Martin, >> >> It is easy to keep it as a contribution if that is what you want. >> We chose an enhancement bug as Script/Xhr/Jsonp communication are core >> functionality and we believe websocket should be too. >> We also used the qx.io namespace of the same reason. >> We believed it might help you >> >> ...but you are right regarding updates... >> >> so we switch it to a contribution with the above namespace. >> >> Stefan >> >>> Hallo Stefan, >>> first of all, thank you very much. I didn?t have time to check out any >>> details but one questions came to my mind right away. Why did you decide to >>> use a pull request instead of a contribution? This topic seems to be so >>> huge and self contained, it could be easily a contribution as well where >>> you would keep the control over your code and don?t have to file a pull >>> request for every other enhancement / bugfix. >>> Regards, >>> Martin >>> Am 12.11.2014 um 15:47 schrieb [email protected]: We have sent a pull request to the qooxdoo. As WebSockets have not been implemented the qooxdoo way with basic, fallback, reconnection, pool, cache, data binding etc, we decided to start it. Any suggestions on it would be appreciated. Stefan -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >>> >>> -- >>> Comprehensive Server Monitoring with Site24x7. >>> Monitor 10 servers for $9/Month. >>> Get alerted through email, SMS, voice calls or mobile push notifications. >>> Take corrective actions from your mobile device. >>> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >>> ___ >>> qooxdoo-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> >> >> >> -- >> Comprehensive Server Monitoring with Site24x7. >> Monitor 10 servers for $9/Month. >> Get alerted through email, SMS, voice calls or mobile push notifications. >> Take corrective actions from your mobile device. >> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >> ___ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > -- > Oetiker+Partner AG tel: +41 62 775 9903 (direct) > Fritz Zaucker+41 62 775 9900 (switch board) > Aarweg 15+41 79 675 0630 (mobile) > CH-4600 Olten fax: +41 62 775 9905 > Schweiz web: www.oetiker.ch > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ qooxdoo-devel
Re: [qooxdoo-devel] WebSocket implementation
Cool ... (although I don't have an immediate application for that, but I know somebody with a Qooxdoo project using web sockets). I also understand the argument about core functionality. But putting it there only helps if 1&1 has the necessary ressources to maintain it (or at least to make sure updates/fixes are checked and integrated in a timely manner). Cheers, Fritz On Thu, 13 Nov 2014, [email protected] wrote: > Hi Martin, > > It is easy to keep it as a contribution if that is what you want. > We chose an enhancement bug as Script/Xhr/Jsonp communication are core > functionality and we believe websocket should be too. > We also used the qx.io namespace of the same reason. > We believed it might help you > > ...but you are right regarding updates... > > so we switch it to a contribution with the above namespace. > > Stefan > >> Hallo Stefan, >> first of all, thank you very much. I didn?t have time to check out any >> details but one questions came to my mind right away. Why did you decide to >> use a pull request instead of a contribution? This topic seems to be so huge >> and self contained, it could be easily a contribution as well where you >> would keep the control over your code and don?t have to file a pull request >> for every other enhancement / bugfix. >> Regards, >> Martin >> >>> Am 12.11.2014 um 15:47 schrieb [email protected]: >>> >>> We have sent a pull request to the qooxdoo. >>> >>> As WebSockets have not been implemented the qooxdoo way with basic, >>> fallback, reconnection, pool, cache, data binding etc, we decided to start >>> it. >>> >>> Any suggestions on it would be appreciated. >>> >>> Stefan >>> >>> -- >>> Comprehensive Server Monitoring with Site24x7. >>> Monitor 10 servers for $9/Month. >>> Get alerted through email, SMS, voice calls or mobile push notifications. >>> Take corrective actions from your mobile device. >>> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >>> ___ >>> qooxdoo-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> >> -- >> Comprehensive Server Monitoring with Site24x7. >> Monitor 10 servers for $9/Month. >> Get alerted through email, SMS, voice calls or mobile push notifications. >> Take corrective actions from your mobile device. >> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >> ___ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- Oetiker+Partner AG tel: +41 62 775 9903 (direct) Fritz Zaucker+41 62 775 9900 (switch board) Aarweg 15+41 79 675 0630 (mobile) CH-4600 Olten fax: +41 62 775 9905 Schweiz web: www.oetiker.ch -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] WebSocket implementation
Hi Martin, It is easy to keep it as a contribution if that is what you want. We chose an enhancement bug as Script/Xhr/Jsonp communication are core functionality and we believe websocket should be too. We also used the qx.io namespace of the same reason. We believed it might help you ...but you are right regarding updates... so we switch it to a contribution with the above namespace. Stefan > Hallo Stefan, > first of all, thank you very much. I didn’t have time to check out any > details but one questions came to my mind right away. Why did you decide to > use a pull request instead of a contribution? This topic seems to be so huge > and self contained, it could be easily a contribution as well where you would > keep the control over your code and don’t have to file a pull request for > every other enhancement / bugfix. > Regards, > Martin > >> Am 12.11.2014 um 15:47 schrieb [email protected]: >> >> We have sent a pull request to the qooxdoo. >> >> As WebSockets have not been implemented the qooxdoo way with basic, >> fallback, reconnection, pool, cache, data binding etc, we decided to start >> it. >> >> Any suggestions on it would be appreciated. >> >> Stefan >> >> -- >> Comprehensive Server Monitoring with Site24x7. >> Monitor 10 servers for $9/Month. >> Get alerted through email, SMS, voice calls or mobile push notifications. >> Take corrective actions from your mobile device. >> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >> ___ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Re: [qooxdoo-devel] WebSocket implementation
Hallo Stefan, first of all, thank you very much. I didn’t have time to check out any details but one questions came to my mind right away. Why did you decide to use a pull request instead of a contribution? This topic seems to be so huge and self contained, it could be easily a contribution as well where you would keep the control over your code and don’t have to file a pull request for every other enhancement / bugfix. Regards, Martin > Am 12.11.2014 um 15:47 schrieb [email protected]: > > We have sent a pull request to the qooxdoo. > > As WebSockets have not been implemented the qooxdoo way with basic, fallback, > reconnection, pool, cache, data binding etc, we decided to start it. > > Any suggestions on it would be appreciated. > > Stefan > > -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > ___ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
