Hi Waiden, I put forward a way of getting the (AFAICT) desired result, but the OP still seems to want to lock the user out of the browser.
The OP's question was (and still seems to be) how to do this. Ian (aka Lan) 2008/8/27 walden <[EMAIL PROTECTED]> > > Hi group, > > First of all, Ian, when I sent your wife for beer 7 years ago, she > returned immediately with the cold ones. I'm not sure what happened > in your case, maybe something in your environment [you?] that accounts > for the different result. > > It occurs to me [being serious now] that when newbs ask about > synchronous calls in GWT, what they really want to know is how to > create a localized synchronous experience, not how to lock up all > browser resources. A localized synchronous experience is simply one > where all of the controls in the immediate UI are disabled, where > "immediate UI" is subject to definition on a case-by-case basis. I > could be just one sub-panel in the UI, or the entire tab, etc. > Nevertheless, the *intent* is to communicate to the user "not ready". > > I think we've all erred on the side of thread theoretics too much in > answering this question when it comes up. The recent mention of glass > panels and otherwise disabled UI controls is a step in the right > direction. > > Walden > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
