Re: [qooxdoo-devel] Asynchronous requests

2009-05-25 Thread Derrell Lipman
On Mon, May 25, 2009 at 1:55 AM, Jim Hunter wrote: > Derrel, > > Setting the request to synchronous and having the entire UI pause until > it finished is exactly what I would want in some cases, but that's not the > behavior I see. With the following code, I get different results then what I > w

Re: [qooxdoo-devel] Asynchronous requests

2009-05-25 Thread Michael Helwig
Hi, thanks for the manifold replies on this topic. However, it was not easily possible to put everything in a function that gets called after the request is finished, at least not without ruining the code structure. The problem was that the method which does the request is part of a seperate Co

Re: [qooxdoo-devel] Asynchronous requests

2009-05-25 Thread Timo Kiefer
hi, i implement this on my applicaiton with events beforeRequest, afterRequest .. put a layer over the whole application or widget with a beforeRequest handler and remove the layer with a afterRequest handler. timo --- Original Nachricht --- Betreff: Re: [qooxdoo-devel] Asynchronous requests

Re: [qooxdoo-devel] Asynchronous requests

2009-05-25 Thread Jim Hunter
If you have a function that you need run after the request is complete, simply call the procedure in the 'completed' event. That is the easiest way to accomplish what you are looking to do. Jim On Mon, May 25, 2009 at 12:57 AM, Michael Helwig wrote: > Hi, sorry for making all these mistakes whe

Re: [qooxdoo-devel] Asynchronous requests

2009-05-25 Thread Michael Helwig
Hi, sorry for making all these mistakes when I started this post. What I wanted to achieve was indeed a *synchronous* request because the code after the reuest relies on the result of the request. As Jim wrote, synchronous requests do not work as I expected them to do. Is there another way to a

Re: [qooxdoo-devel] Asynchronous requests

2009-05-24 Thread Jim Hunter
Derrel, Setting the request to synchronous and having the entire UI pause until it finished is exactly what I would want in some cases, but that's not the behavior I see. With the following code, I get different results then what I would expect. Here is the code: var rq = new qx.io.remote.Reque

Re: [qooxdoo-devel] Asynchronous requests

2009-05-24 Thread Derrell Lipman
On Sun, May 24, 2009 at 5:44 PM, Michael Helwig wrote: > Hi, > I'm trying to do an asynchronous request, but it doesn't work. > You're setting the "asynchronous" property to false, so you're in fact, trying to do a *synchronous* request, not an async one. You probably really don't want to do that

Re: [qooxdoo-devel] Asynchronous requests

2009-05-24 Thread Michael Helwig
Okay, seems that my check was wrong, it should read if(req.isAsynchronous()) //... which works as expected. But still it seems that the request is not asynchronous. I do the folling in Application.js: [CODE] var ConfigInfo = hbtables.Config.getInstance(); alert(ConfigInfo.__tables); [/CODE]

[qooxdoo-devel] Asynchronous requests

2009-05-24 Thread Michael Helwig
Hi, I'm trying to do an asynchronous request, but it doesn't work. [CODE] var req = new qx.io.remote.Request(url, "GET", "application/xml"); req.setAsynchronous(false); req.addListener("completed", function(response){ //... }, this); [/CODE] Adding [CODE] if(req.isAsynchronous)