al0, No, actually it's not a workaround. Its an even better user experience, because if the controls on the page still look like they are active (but they're not because the browser is locked up), then the app is lying to the user, whereas if the controls are explicitly inactive, then we're telling the truth.
Your point about code clarity is valid. But consider this tradeoff: Option A: your code is clear, but your user is confused and frustrated trying to use your site Option B: your code is spaghetti, but your user is delighted and keeps coming back Sure, these are extremes, chosen to make the point, but which do you choose? Walden On Aug 27, 9:04 am, al0 <[EMAIL PROTECTED]> wrote: > Hi, > > Your use of a modal dialog, greyed button .... constitutes just a > workaround ror and (absent) synchronous call. If latter would be > present your code would be min. 3 times shorter and (IMHO) much more > clear. > > Oleksandr --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
