Re: [qooxdoo-devel] list and dblclick event

2009-03-07 Thread Petr Kobalíček
Thanks, Currently I will stay with first method, but it's good to know second one :-) Cheers - Petr 2009/3/8 Derrell Lipman : > 2009/3/7 Petr Kobalíček >> >> Hi Derrell, >> >> thanks for your post. I'm using quite similar way except in dblclick >> handler. What's happen if I double click to emp

Re: [qooxdoo-devel] list and dblclick event

2009-03-07 Thread Derrell Lipman
2009/3/7 Petr Kobalíček > Hi Derrell, > > thanks for your post. I'm using quite similar way except in dblclick > handler. What's happen if I double click to empty area (not list item > in list) and where e.getTarget() will point ? (I think to list > itself). > > Correct way for me is something li

Re: [qooxdoo-devel] list and dblclick event

2009-03-07 Thread Petr Kobalíček
Hi Derrell, thanks for your post. I'm using quite similar way except in dblclick handler. What's happen if I double click to empty area (not list item in list) and where e.getTarget() will point ? (I think to list itself). Correct way for me is something like this: list.addListener("dblclick", f

Re: [qooxdoo-devel] list and dblclick event

2009-03-07 Thread Derrell Lipman
On Sat, Mar 7, 2009 at 6:17 PM, Petr Kobalíček wrote: > Hi, > > how is the best and preffered way to use dblclick event on lists > (qx.ui.form.List). I want to do action when user double clicks on list > item, but I don't know how to clearly do it. > > For example my current way is to remember las

[qooxdoo-devel] list and dblclick event

2009-03-07 Thread Petr Kobalíček
Hi, how is the best and preffered way to use dblclick event on lists (qx.ui.form.List). I want to do action when user double clicks on list item, but I don't know how to clearly do it. For example my current way is to remember last clicked item and dblclick is using it. So my question is, is the

Re: [qooxdoo-devel] HtmlArea optimized build

2009-03-07 Thread Petr Kobalíček
Hi Thomas, this is when I create instance of HtmlArea (browser load is OK). I think that this problem is here very long time, first time I tested HtmlArea there was similar problem, after this I used only builds without privates optimization and I never had this problem again, but I think it shoul

Re: [qooxdoo-devel] HtmlArea optimized build

2009-03-07 Thread thron7
Petr, > Hi, > > I tested htmlarea and there is something wrong when building optimized > build. When I try to create it, it throws this error: > > this.__vo.__vs is undefined This is when you load it in the browser, right?! Or at some special action?! Is this with qooxdoo 0.8.2? Ok, please file

Re: [qooxdoo-devel] qxbuild for 0.8.2 ready

2009-03-07 Thread Jean-Baptiste BRIAUD -- Novlog
On 7 Mar 2009, at 15:56, Petr Kobalíček wrote: > Hi Jean, > > thanks :) > >> About the loading bar : when finish, why only remove >> body.removeChild(pbor); and why not also remove >> body.removeChild(pbar); ? > > When you remove pbor (progress border), the pbar is not active anymore > and I hope

[qooxdoo-devel] 0.8.2

2009-03-07 Thread A.Yerenkow
Hello guys! In current 0.8.2 I'm at last can bind form inputs to custom object (which didn't work for me in 0.8.1); My object is simple getter-setter wrapper for few values; I'm binding it like that: var manager = new qx.ui.form.RadioButton("Manager"); var client = new

Re: [qooxdoo-devel] qxbuild for 0.8.2 ready

2009-03-07 Thread Petr Kobalíček
Hi Jean, thanks :) > About the loading bar : when finish, why only remove > body.removeChild(pbor); and why not also remove > body.removeChild(pbar); ? When you remove pbor (progress border), the pbar is not active anymore and I hope that browser's garbage collector will free all of these:) > A

Re: [qooxdoo-devel] qxbuild for 0.8.2 ready

2009-03-07 Thread Jean-Baptiste BRIAUD -- Novlog
it works fine for me, thanks for your work ! About the loading bar : when finish, why only remove body.removeChild(pbor); and why not also remove body.removeChild(pbar); ? About the starting page that contain the loading bar, few idea I'm not sure how doable it is : have an HTML page where

Re: [qooxdoo-devel] Closable tabs in 0.8

2009-03-07 Thread Petr Kobalíček
Thanks tobi, I'm wondering why it's not in qooxdoo, because it's really simple:) Cheers - Petr 2009/3/7 Tobias Oetiker : > Hi Petr, > > assume result is a  qx.ui.tabview.Page >  and   remove_tab a function to call remove with result on the > qx.ui.tabview.TabView > >  var button = result.getBut

Re: [qooxdoo-devel] Closable tabs in 0.8

2009-03-07 Thread Tobias Oetiker
Hi Petr, assume result is a qx.ui.tabview.Page and remove_tab a function to call remove with result on the qx.ui.tabview.TabView var button = result.getButton(); var cross = new qx.ui.basic.Image("decoration/window/close-inactive.png").set({marginRight : -3 }); cross.addListener('cli

Re: [qooxdoo-devel] Closable tabs in 0.8

2009-03-07 Thread Petr Kobalíček
I want to reopen discussion on closable tabs. Currently nearly each of all my tab pages needs some way how to close it (I'm creating buttons somewhere to do that) and I think that others have same problems. So is possible to create tab page with close button ? Some hints will be nice:) Cheers -

[qooxdoo-devel] qxbuild for 0.8.2 ready

2009-03-07 Thread Petr Kobalíček
Hi devs, after some time hacking qooxdoo 0.8.2 I completed port of qxbuild for 0.8.2. It's not excellent, but it works and there is also possibility to add simple progress bar for loading javascript files. Changes to previous versions: - There are no contribs now, if you need contrib, you need

[qooxdoo-devel] HtmlArea optimized build

2009-03-07 Thread Petr Kobalíček
Hi, I tested htmlarea and there is something wrong when building optimized build. When I try to create it, it throws this error: this.__vo.__vs is undefined I think this is related to privates optimization, because when i try to build HtmlArea without this kind of optimization there is no such e

Re: [qooxdoo-devel] listener activation looks broken

2009-03-07 Thread Kenneth Tilton
Fritz Zaucker wrote: > On Sat, 7 Mar 2009, Kenneth Tilton wrote: > >> Fritz Zaucker wrote: >>> On Fri, 6 Mar 2009, Kenneth Tilton wrote: >>> No, but we use Chrome and we do need the speed--the app is a fairly hairy datamining deal (so there is a lot of work to do in JS) and the ap

[qooxdoo-devel] Remarks on the qxbuild discussion

2009-03-07 Thread Fritz Zaucker
My observation from the outside (not really involved in building/loading questions): - There was a lot of help offered on the mailing list by the Qooxdoo developers to help you come up with an environment for your special applications that is compatible with the Qooxdoo build system (and thus

Re: [qooxdoo-devel] listener activation looks broken

2009-03-07 Thread Fritz Zaucker
On Sat, 7 Mar 2009, Kenneth Tilton wrote: > Fritz Zaucker wrote: >> On Fri, 6 Mar 2009, Kenneth Tilton wrote: >> >>> No, but we use Chrome and we do need the speed--the app is a fairly >>> hairy datamining deal (so there is a lot of work to do in JS) and the >>> application is one where users espe

Re: [qooxdoo-devel] listener activation looks broken

2009-03-07 Thread Kenneth Tilton
Fritz Zaucker wrote: > On Fri, 6 Mar 2009, Kenneth Tilton wrote: > >> No, but we use Chrome and we do need the speed--the app is a fairly >> hairy datamining deal (so there is a lot of work to do in JS) and the >> application is one where users especially will want a highly responsive >> system.

Re: [qooxdoo-devel] listener activation looks broken

2009-03-07 Thread Fritz Zaucker
On Fri, 6 Mar 2009, Kenneth Tilton wrote: > No, but we use Chrome and we do need the speed--the app is a fairly > hairy datamining deal (so there is a lot of work to do in JS) and the > application is one where users especially will want a highly responsive > system. We do not want to leave any CP

Re: [qooxdoo-devel] qxbuild

2009-03-07 Thread Jean-Baptiste BRIAUD -- Novlog
+1, nothing else to add. On 6 Mar 2009, at 23:46, Petr Kobalíček wrote: > I have only one thing to say:) > > There are developers (including me and Jean) that wants to use qooxdoo > without python build tools (I have python, I'm building qxbuild:) ). I > think that we shouldn't talk about why the