On Apr 7, 2011, at 7:04 PM, Carter R. Harrison wrote:
On Apr 7, 2011, at 6:38 PM, Nick Zitzmann wrote:
On Apr 7, 2011, at 4:24 PM, Carter R. Harrison wrote:
I really appreciate all of your help. I gave your suggestion a shot and
I've run into problems. Here's what happens.
1. I
On Mar 30, 2011, at 4:09 PM, Nick Zitzmann wrote:
On Mar 30, 2011, at 2:05 PM, Carter R. Harrison wrote:
2. What is the best way to implement it?
Put your CoreData code into a framework shared by your applications. And
use distributed notifications to keep the applications in sync.
On Apr 7, 2011, at 4:24 PM, Carter R. Harrison wrote:
I really appreciate all of your help. I gave your suggestion a shot and I've
run into problems. Here's what happens.
1. I create a new NSManagedObject in my main application. It gets inserted
into the context.
2. I save the
On Apr 7, 2011, at 6:38 PM, Nick Zitzmann wrote:
On Apr 7, 2011, at 4:24 PM, Carter R. Harrison wrote:
I really appreciate all of your help. I gave your suggestion a shot and
I've run into problems. Here's what happens.
1. I create a new NSManagedObject in my main application. It
I'm working on a Mac Application that will have a helper application that is
always running in the background (even if the main application is not currently
running). Currently the main application uses Core Data to manage persistent
objects. I'd like to setup the helper application to be
On Mar 30, 2011, at 1:45 PM, Carter R. Harrison wrote:
I'm working on a Mac Application that will have a helper application that is
always running in the background (even if the main application is not
currently running). Currently the main application uses Core Data to manage
persistent
On Mar 30, 2011, at 4:03 PM, Nick Zitzmann wrote:
On Mar 30, 2011, at 1:45 PM, Carter R. Harrison wrote:
I'm working on a Mac Application that will have a helper application that is
always running in the background (even if the main application is not
currently running). Currently the
On Mar 30, 2011, at 2:05 PM, Carter R. Harrison wrote:
2. What is the best way to implement it?
Put your CoreData code into a framework shared by your applications. And use
distributed notifications to keep the applications in sync.
So when one application saves the data store, then
On 2011 Mar 30, at 13:09, Nick Zitzmann wrote:
Something like that. Or you can send a notification containing the IDs of the
managed objects that were changed in the other app, and have your handler
re-fault its managed objects if necessary so that it'll have the latest
information when
