Hi what you want is very simple (maybe 30 minutes of work). all you need is to copy the code from http://code.google.com/intl/de/apis/gears/sample.html (ManagedResourceStore Demo) app to your app and modify it how you want. But all you need is already in that code.
About your questions the difference between createStore() and createManagedStore() is that first one creates a ResourceStore (http://code.google.com/intl/de/apis/gears/ api_localserver.html#ResourceStore) and the second one creates a ManagedResourceStore (http:// code.google.com/intl/de/apis/gears/ api_localserver.html#ManagedResourceStore) Difference between those 2 is that first one does not use a manifest file and second one use. links in manifest are relative to the base_url (http://code.google.com/ intl/de/apis/gears/api_localserver.html#manifest_file) as you can see there is documentation for everything, just need to read it. http://www.insideria.com/2009/01/google-gearsa-great-tool-to-en.html this is my article about gears and what can be used for. have a section for caching (with a tutorial) On Mar 18, 9:46 pm, Quicksilver <[email protected]> wrote: > Okay, I'm sorta pulling my hair out. Here's the deal, I just want to > incorporate some very simple LocalServer caching for a CMS app. No > fancy offline support, no weird DB stuff, just cache everything to run > faster (sorta like what Wordpress is doing). But so far, every > example I've looked at, well, sucks. At least insofar that I haven't > been able to adapt a single technique. And the documentation sucks > pretty hard too, like trying to figure out what the difference between > createStore() and createManagedStore() is. Frankly, I couldn't tell > you given everything I've read. My goal is to make this as *simple* > as possible, while still being properly functional. > > So, let me outline my scenario. I've dropped the gears_init.js file > on the server, and created a manifest.json file. They are both in / > html/js/gears on the server. I want to plug a button into the > bottom.jsp template file to enable or disable gears based on whether > it is or not already. Here's the code as I've managed so > far:http://pastebin.com/f3d5dd4cf > > The other thing I'm not clear on, does the manifest.json file need to > be a path relative to the gears_init.js file (so "manifest.json"), or > something absolute (like "/html/js/gears/manifest.json"). I've also > had to strip out stuff like checkForUpdate() because when it's in > there, I get errors about the function not being defined. I'm just > surprised how difficult this is proving overall.
