+1. When the user presses "load / submit / ..." on my app, I enable the glass pane, and they have to wait until the submit has completed successfully. I see nothing wrong with this approach:
PopupPanel loadingDialog = new PopupPanel(); loadingDialog.setWidget(loadingImageAnimation); loadingDialog.setGlassEnabled(true); loadingDialog.center(); .. do the work onSuccess and onFailure callback loadingDialog.hide(); On Jun 10, 9:28 am, Carl Pritchett <bogusggem...@gmail.com> wrote: > > Your proposal is interesting. But as a user, if I have to wait, I > > leave... So many be an application needing some "wait a minute" popup > > is not a good approach for the future. > > I wouldn't popup (block user interaction) over the whole page! Just > the component that needs to load. In fact you don't even need to block > user interaction. I just do it in my application because (for example) > the user has clicked refresh on a component and any interaction with > the refreshing component would be invalid. So in my case partial > blocking the UI is better for the user - they can go on interacting > with other parts of the app (we have a multiple "portal like" windows) > > Carl. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
