Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basic usage clarification #154

Closed
maxfi opened this issue Feb 24, 2016 · 1 comment
Closed

Basic usage clarification #154

maxfi opened this issue Feb 24, 2016 · 1 comment

Comments

@maxfi
Copy link

maxfi commented Feb 24, 2016

When in offline mode how do I know when the collections are ready?

  • Ground.isReady() appears to become true when a collection has successfully been grounded when online but doesn't become true when offline.
  • Ground.isResumed() appears to become true when the grounded collection is ready, even when offline, but appears to become true prior to the collections being fully loaded with data.

Also, could someone please clarify the following from the README:

Example of different patterns. Grounding a Meteor.Collection will attach the cache, resume and cross tabs update offline

Basically what I'm looking to achieve is to have all my collections cached (with all records) into localStorage so that when the app is loaded when offline (utilizing appcache) it works as it would normally whilst online. Ie, the user is able to make changes to collections etc which are then then synced when the client gets an internet connection. Is there anything other than grounding the collections that I need to do to get this to work?

@raix
Copy link

raix commented Apr 6, 2016

I've released 2.0.0-alpha.1 Notes about the new version, migration and what it doesn't do - Theres a loaded event, let me know what you think

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants