Hi

> I'm not sure I understand this requirement. If you're talking about a
> GWT tab widget, no user data will be lost when the tab "closes". In a
> TabPanel, a Tab close event is usually associated with moving focus to
> another tab. No data loss occurs.

Even if that's the case, I still need to save the data that's been
entered onto my tab at that point.

> Any browser actions that can could result an irretrevable data loss or
> irreversable write are , by design, synchronously cancelable (CGI
> post, Window.onClose). Does this app. use a TabPanel in a non-standard
> way?

Nope. All standard.

> For what it's worth, I've also found that it's helpful to simply
> implement  automatic, asynchronous "save draft" behavior.Given the
> machinery that GWT provides, saving a user's data on their behalf is
> nicer than the "old style" technique where one would ask if changes
> should be preserved. This technique also provides a nice segue into
> some kind of application-specific history support.

The user may not want to save thier changes.

> This technique supports a "review before post" step. In this step the
> draft data are presented for review before posting to the server. The
> review -> post transition is synchronous and interruptible.

No with you here. Can you explain more?

> If "canceling the close"  is really the behavior you want, try
> scheduling a deferred command in the onCloseHandler that sets focus to
> the tab if the user does not want to close said tab.

Setting focus to the tab stops it from closing? :-s

-- 
Thanks
Paul

Paul Grenyer
e: [email protected]
w: http://www.marauder-consulting.co.uk
b: paulgrenyer.blogspot.com

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to