Re: [qooxdoo-devel] Remote table columns from backend problem.

2010-05-27 Thread panyasan
Yan Guiborat wrote: > > I don't like that much race conditions, so I used a synchronous call to > get columns names and ids, into the constructor. Like this, I'm sure the > table is in a stable state when constructed. > Yes, asynchronicity can create real headaches, but in my opinion, if you

Re: [qooxdoo-devel] Remote table columns from backend problem.

2010-05-27 Thread Yan Guiborat
Hi, I find a workaround anyway, I don't like that much race conditions, so I used a synchronous call to get columns names and ids, into the constructor. Like this, I'm sure the table is in a stable state when constructed. I'm now using this->debug, have to loose some bad habits ;-) I am JSON e

Re: [qooxdoo-devel] Remote table columns from backend problem.

2010-05-26 Thread panyasan
Hi Yan, might it hae something to do with all the alert() statements you're using? Is it the same behavior if you use this.debug() instead, which doesn't block the javascript thread? Other than that, why are your eval'ing your result from the rpc service method? you can simple return an indexed

[qooxdoo-devel] Remote table columns from backend problem.

2010-05-25 Thread Yan Guiborat
Hi List, I'm trying to set the column model of my remote table from the backend. Everything works fine beside this. Here is part of my model code: qx.Class.define("licnet.modellistagentadmin", { extend : qx.ui.table.model.Remote, construct: function() { this.base(arguments);