On 09/11/2009, at 5:03 PM, Martin Hewitson wrote:
Thanks, Rob. I do have this book, but I sort of skipped the section about
multithreading (where the export example is buried), but I've found it now.
Yes, it's kind of a shame that it's buried in there. I initially skipped it too.
In my
Dear list,
I've been digging around for export and import strategies to allow me
to export parts of a core data model. In more detail, I have a set of
categories, each of which contains a set of meetings. Each meeting has
a fairly complex object graph below it (agenda, agenda items,
On 2009 Nov 08, at 11:18, Martin Hewitson wrote:
I want to allow the user to export a meeting which can then be
imported by someone else using the same application.
Looks like a document to me. Why not make this a document-based
application? NSPersistentDocument. This has been done
On Sun, Nov 8, 2009 at 12:21 PM, Jerry Krinock je...@ieee.org wrote:
Looks like a document to me. Why not make this a document-based
application? NSPersistentDocument. This has been done before :)
It sounds to me more like Martin wants to export a fragment of his
document, much like someone
On 09/11/2009, at 5:18 AM, Martin Hewitson wrote:
I've been digging around for export and import strategies to allow me to
export parts of a core data model. In more detail, I have a set of
categories, each of which contains a set of meetings. Each meeting has a
fairly complex object
Thanks, Rob. I do have this book, but I sort of skipped the section
about multithreading (where the export example is buried), but I've
found it now.
Thanks to the others who replied as well. I think this has set me on
the right track.
@Jerry: I chose not to use a document-based design
