You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey Aaron! I attended your presentation on Core Data Concurrency @ 360iDev, thanks btw!!! I am just starting to dig through your demo code to try and start implementing some of this in a project I am working on. The question that comes to mind right away is where do I store this CoreDataStack object for access across multiple views in my app.
The easy way of course is to put it in the AppDelegate. But grabbing from the AppDelegate all the time is not really good practice.
I could create it in my AppDelete and inject it into my view controllers as needed. Wondering why you example did not take this approach. This also gets messy if you up a storyboard and you have to change where/how its gets injected.
Is each view supposed to create its own CoreDataStack object? That doesn't feel right to me for some reason, although it may very well be ok as I have no idea ;)
The text was updated successfully, but these errors were encountered:
Hey Aaron! I attended your presentation on Core Data Concurrency @ 360iDev, thanks btw!!! I am just starting to dig through your demo code to try and start implementing some of this in a project I am working on. The question that comes to mind right away is where do I store this CoreDataStack object for access across multiple views in my app.
The easy way of course is to put it in the AppDelegate. But grabbing from the AppDelegate all the time is not really good practice.
I could create it in my AppDelete and inject it into my view controllers as needed. Wondering why you example did not take this approach. This also gets messy if you up a storyboard and you have to change where/how its gets injected.
Is each view supposed to create its own CoreDataStack object? That doesn't feel right to me for some reason, although it may very well be ok as I have no idea ;)
The text was updated successfully, but these errors were encountered: