Re: To use ABPerson or not?
Re: To use ABPerson or not?
- Subject: Re: To use ABPerson or not?
- From: Stefan Pantke <email@hidden>
- Date: Tue, 16 Mar 2004 04:02:06 +0100
Cauri,
since each AB record is uniquely identified, there is in fact no need
to store the records inside your application.
How about storing the unique IDs inside your app and reference
the real data using the IDs.
On the other side, it might be interesting to keep a backup of
all records in your local db, just in case some records get removed
from AB. Then, you could inform the user and ask or the correct
reaction:
- Recreate again from your internal backup
- Remove in your internal db as well
Speaking of efficiency, using some extra disk space should be no
problem,
since our app has some extra functionality and your user some extra
benefit.
Stefan
Am 16.03.2004 um 03:39 schrieb cauri:
Newbie trying to figure it out.
I have begun design of a cocoa application that will reference os x
address book records as part of its funtionality. I worry however,
that someone may erase a record in the address book program for
example and my app will have a blank space. How do I solve this? Do I
create a custom subclass of ABPerson and copy the data of the person
the user wants into this custom subclass, write it to disk and then
use some form of notification to keep the data synchronised? I'm a
little confused, what is the most efficient way to do this?
cauri
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.