Actually, not quite. Think of the app to distribute as an image created while online: we capture some static files, and load some data into gears' sqllite DB. Now we'd like to distribute this image to a number of machines offline through an external harddrive or floppy disk. I'd imagine, we'd have to copy gears specific data from the Application Data folder to the relevant internet directories on these machines. This is presumably a hack, so I was hoping for a cleaner solution.
On Aug 30, 7:12 pm, Tac Tacelosky <[email protected]> wrote: > Not really. You could possibly put something together that basically > invoke the online app and loaded some data, but the amount of work > required to assemble the initial offline app wouldn't be worth the > effort. > > If the initial offline part were trivial enough (e.g. filling out a > form), you could distributed the offline part as a series of static > page (html, css and js), then invoke your site online for the final > step. But there's so little you'd be able to do, no database, no > searching, etc. > > How about re-framing it as "we have this offline app, but you need to > access it online to install it"? Because that's effectively what it > is. > > Tac > > On Sun, Aug 30, 2009 at 5:19 AM, Sam Donaldson<[email protected]> wrote: > > > Any help would be appreciated, thanks. > > > On Aug 25, 9:23 pm, Sam Donaldson <[email protected]> wrote: > >> Hi, > > >> I'm helping a non-profit with making an offline version of their > >> application. From my reading, it seems like gears is great for the > >> online to offline case - while online, user installs the gears plugin, > >> does a sync to capture requisite files, and goes offline. My question > >> is about the offline to online case. We'd like to distribute our > >> application as something similar to a jar file, maybe via a disk or > >> harddrive, and utilize the application in offline mode first and sync > >> upon connecting to the internet. Is there a clean way of doing this? > > >> Thanks.
