Re: New Tiger NSDocument API's
Re: New Tiger NSDocument API's
- Subject: Re: New Tiger NSDocument API's
- From: j o a r <email@hidden>
- Date: Mon, 13 Jun 2005 09:53:19 -0700
On 13 jun 2005, at 09.01, Philip Ershler wrote:
The files I need to read (and ultimately write) are custom format
files that come from a data acquisition system that has been
designed and built in our institute. The files consist of a 1024
byte header followed by a stream of 16 bit integers. Total files
size may run from several hundred kilobytes to 1 or 2 gigabytes.
That would explain why you wouldn't want to use the standard
"loadDataRepresentation:ofType:" methods. Thanx.
Also, why are you using functionality from CF? Do you have a
special reason to not use the Cocoa ("NS") API? Is the file too
large to be read all at once, and in that case, why not use
NSFileHandle?
I was just (perhaps naively) following the suggestion in the
NSDocument template that I got when I started a Cocoa Document
based app.
I guess it all comes down to overriding the right methods. Check here:
<http://developer.apple.com/documentation/Cocoa/Conceptual/Documents/
Tasks/FAQ.html#//apple_ref/doc/uid/20000954-1081125-BAJIGEFI>
If you use the "readFromURL:ofType:error:" methods, you have access
to the file URL in question.
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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