You have to think about what kind of UI the users actions have caused. For instance, if you would expect all inputs to become disabled (or at least the one which would generate more async calls). Perhaps also some kind of waiting indicator that you are in an async call.
On Wed, Mar 4, 2009 at 10:15 PM, rlaferla <[email protected]> wrote: > > How is everyone managing to implement sequential workflows when GWT > only allows async calls? > > I have a series of panels that user must respond to in sequence and > their answers may lead to a different path of panels (warnings, error > panels, etc..) I think every GWT programmer working on a large > project must have run into this. I'm interested in what strategies/ > techniques/code you used to help keep the complexity down. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
