I think this is not taking Gears to full usability. True, 99% use it online/offline, but this is because it does not fully support working offline only. I can thing of many applications that will be downloaded from a web page, and will be very useful with a local database, but the developer will not provide a server. This is especially true for RIAs.
On Sep 2, 5:24 am, Eduard Martini <[email protected]> wrote: > Glad I could help ;) > > On Sep 1, 5:22 pm, "gal.gefen" <[email protected]> wrote: > > > As I have said, the application will NOT communicate with a server, it > > will be always offline. > > And I can't tell the user to find it's user name, profile, etc > > depending on its OS and other parameters. > > Its good for a developer, but not a user. > > This is why I need some clean way to do it from an app running in the > > browser, or from the browser. > > > On Sep 1, 6:24 am, Eduard Martini <[email protected]> wrote: > > > > I think this is not a good idea for most of the applications, because > > > sync online to offline -> work on offline db -> backup offline db -> > > > more work on offline -> sync offline to online -> restore offline -> > > > resync to online => big mess. > > > > Right now you can save the DB file somewhere else. It is a normal > > > sqlite DB that can be browse/accessed locally with any sql browser. > > > And is not "hidden" from user: > > > >http://code.google.com/apis/gears/api_database.html#ResultSet-fieldBy... > > > see Location of Database File > > > > On Aug 29, 9:21 pm, "gal.gefen" <[email protected]> wrote: > > > > > I am writing a web application that can run completely offline (never > > > > communicate with the server), but uses the Gears database. > > > > > I must allow the user to backup the data (and possibly restore it), > > > > but Gears hides the database from the user. > > > > > I would think there should be > > > > > 1) an option in the tools->Gears settings menu to backup/restore a db. > > > > 2) a method in the API that allows to get the db location (so I can > > > > ask the user to copy it) + a specification of what will allow a > > > > correct restore. > > > > > Does anyone else needs this ? > > > > Any advice what to do right now for backup ?
