• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: New Tiger NSDocument API's
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New Tiger NSDocument API's


  • Subject: Re: New Tiger NSDocument API's
  • From: Philip Ershler <email@hidden>
  • Date: Mon, 13 Jun 2005 10:27:39 -0600


On Jun 13, 2005, at 10:12 AM, Bill Bumgarner wrote:

On Jun 13, 2005, at 9:01 AM, 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.


Given that the files will be the data spewed by the DAQ system, it is unlikely that your application will need to write said files? That is, the files containing the acquired data will be treated more like something you import into your application and less like a true document?

At this point, I'm just trying to open and display data from some existing DAQ data files. Ultimately, I'm going to be writing an application that streams data from the DAQ system (via a firewire interface that I have designed) to disk. This application will also need to be capable of opening and displaying existing files.



Given my assumption, then I would recommend sticking with a document based application where each document is effectively a data analysis "session".

I chose (perhaps incorrectly) the Document app because each recording epoch from the DAQ will get written to its own file.


That is, an individual document may contain configuration information or, even, data that has been imported.

Indeed, each document will contain configuration information and the acquired data.


Then, add an "import" menu item (or support drag and drop) such that your app can import or accept the raw data files sourced from the DAQ system.

I'm a bit confused about your "import" suggestion. The files in question "belong" to this application. What I'm trying to do at this point is just use "Open" from the File menu to open and display a DAQ file.


Thanks for your comments.

Phil


b.bum


_______________________________________________ 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
  • Follow-Ups:
    • Re: New Tiger NSDocument API's
      • From: Bill Bumgarner <email@hidden>
References: 
 >New Tiger NSDocument API's (From: Philip Ershler <email@hidden>)
 >Re: New Tiger NSDocument API's (From: j o a r <email@hidden>)
 >Re: New Tiger NSDocument API's (From: Philip Ershler <email@hidden>)
 >Re: New Tiger NSDocument API's (From: Bill Bumgarner <email@hidden>)

  • Prev by Date: Re: Bug in [path containsPoint]?
  • Next by Date: Re: Bug in [path containsPoint]?
  • Previous by thread: Re: New Tiger NSDocument API's
  • Next by thread: Re: New Tiger NSDocument API's
  • Index(es):
    • Date
    • Thread