Document infrastructure in a DB-based app
Document infrastructure in a DB-based app
- Subject: Document infrastructure in a DB-based app
- From: Christian Schneider <email@hidden>
- Date: Mon, 20 Sep 2004 00:24:02 +0200
Hi list,
we've got an application that handles four different document types. As it
has unfortunately grown in quite an unstructured way I'd like to change it
to support Cocoa's document infrastructure. However, while reading up on
the topic I noticed the strong bias on file based documents - our
application writes directly to a database backend.
As I understand it dataRepresentationOfType: and
loadDataRepresentation:ofType: would be the primary methods to load and
save document data. In our case what would have to be done is pervert these
methods to write and read data from the data base.
I'm not sure whether the gained ease of use with respect to window
management as well as overall clarity of the code's structure would be
counterweighted by hacking around one of the bases of the document
infrastructure.
Any thoughts on the topic would be highly appreciated.
chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden