On 9/19/07, Simon Lessard <[EMAIL PROTECTED]> wrote: > Or... I assume the listener will only be called once, when the first request > is sent, if there's queued events? If so even JavaScript trick won't do the > trick.
Currently, if you queue an event while another is already processing, you don't get any status changed notification. Now, we could change that. Nothing says the API can't be that we give you both a new status and an old status, and everytime a new request is queued, you just get BUSY/BUSY, instead of READY/BUSY or BUSY/READY. That'd handle the cleanup end of this, but not the launching end. We could wrap this up into a non-crappy event object, with getOldStatus(), getNewStatus(), and *also* getParameters(), pass that to the status listener, and then you have pretty much everything you want. -- Adam > > > On 9/19/07, Simon Lessard <[EMAIL PROTECTED]> wrote: > > Hello Adam, > > > > See comments inline. > > > > Thanks, > > > > ~ Simon > > > > > > On 9/19/07, Adam Winer < [EMAIL PROTECTED]> wrote: > > > A couple problems: > > > - It'd be easy enough to list the replaced targets when going from > busy->ready, > > > but on ready->busy, we don't know what is going to be replaced (the > server > > > will figure that out). > > > > > > Yeah, that's why we want to place the icon beside the source, not the > replaced items. Not as intuitive, but at least tell the user there's > something going on. We want that mainly for some dynamic LoV that sometimes > requires a database query requiring a 1~2 second delay, and the marketing > somehow does not like GMail style that much, although I might be able to > have it accepted if the other solution is not possible. > > > > > > > - If you have a series of queued events, you don't get busy->ready until > > > all are completed, so if we had this, you'd see a series of icons show > > > up one by one, and none would go away until all the requests > completed. > > > > > > Ah, that's indeed a show stopper. Unless I do some little JavaScript trick > in the listener to make sure only one icon is visible at a time. > > > > > > > -- Adam > > > > > > > > > On 9/19/07, Simon Lessard < [EMAIL PROTECTED]> wrote: > > > > Hello all, > > > > > > > > Is there a way to get the PPR source node form a JS > StateChangeListener? > > > > Maybe from TrPage or from TrRequestQueue? The use case would be an > icon > > > > (status indicator like) placed beside input fields and showing only > when the > > > > input sent a PPR request. > > > > > > > > > > > > Regards, > > > > > > > > ~ Simon > > > > > > > > > > > > >
