Hi Combi, If all you want is for the user to be able to view your application without actually performing any operations requiring persistence, then your approach should work and meet your needs. However, there are more than a few reasons why using something like Gears to take your application offline would make a lot of sense:
1) For cases where you do want to handled operations requiring persistence. 2) As a developer, you don't have to go through the hassle of tracking all the resources that need to be packaged into a zip when the user clicks "Save as HTML page" (also, the term "Save as HTML page" doesn't clearly indicate that this will allow me to use the entire application offline, so you'll have to use a more informative term that might seem alien to the user), 3) Your users can use the application as they normally would and it will just work, whether they are connected or not. 4) You can take advantage of some of the other useful features in Gears such as desktop shortcuts or multiple file upload, if they make sense for your application. This is probably more of a Gears question than something GWT-related, so I would encourage you post up about the question on the Gears group to see other reasons why it might be a good choice, or why implementing a "Save as HTML page" feature might be enough for your needs. Gears group: http://groups.google.com/group/gears-users Hope that helps, -Sumit Chandel On Sun, Feb 22, 2009 at 3:21 PM, combi <[email protected]> wrote: > > Hi all, > > I just made a working proto framework on top of GWT and SmartGWT that > allows, among other things, to take an application offline using "save > as HTML page...". > > This works fine with Firefox and Chrome and I think even Safari, so I > would like your opinions on the subject. > > The use-case to take the app offline: > > 1) the user at some point clicks on "take application offline". > 1b) the user gets a zip file downloaded to be extracted anywhere (no > need to be local admin). This is for image and resource issues and is > needed only one time per machine. > 2) the user use the "save as..." feature of the browser and saves the > page into the root folder of the zip extract. > 3) the user opens the file locally (with a url file:///something) and > the application runs fine. > 4) the user can save this offline work anytime by using "save..as" > again. > 5) the user can commit changes to the server by going to the online > site and uploading the local file. > > No need for a local HTTP server, nor a database. > Of course you have to handle in your AJAX GUI the online/offline cases > and "read from DOM cache" instead of RPC. > > Thanks for your comments. > > -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 -~----------~----~----~----~------~----~------~--~---
