Thanks for your answer !
1) You missed the point. The proposed approches DOES allow to take
offline and persist offline-made changes.
The approach is based on the fact that when making "save as" in
Firefox or Chrome, the content of the DOM **at the time of saving** is
persisted, not the DOM state just after page load (like in IE). And
this DOM can be manipulated offline with scripting.
It's easy to code for example a "take-offline email client", that
allows to write emails offline and save them. Imagine your gmail saved
on an USB key.... and working anywhere without prior requirement,
local admin rights or installation.
2) as a developer, I do LOVE been hassled by technical problems that
will allow users NOW (in march 2009) to work offline anywhere with
ZERO-INSTALL but Firefox or Chrome available on the client machine as
only requirement.
So... remember you read it here first ;-)
Cheers,
-Combi
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
