Re: Advice request from newbie
Re: Advice request from newbie
- Subject: Re: Advice request from newbie
- From: Ondra Cada <email@hidden>
- Date: Fri, 21 Sep 2001 18:53:32 +0200
Andrea,
>
>>>>> Andrea Perego (AP) wrote at Fri, 21 Sep 2001 18:22:03 +0200:
AP> These peculiarities (and my lack of Cocoa experience!) make me dubious
AP> about embracing the standard Cocoa model for document driven
AP> applications, with due subclassing, or skipping it altogether. Of course,
AP> a rather easy way (?) would be to equate: a spectra file <-> a Cocoa
AP> document
It rather depends on the UI considerations. If the spectra file should be
_USED AS A DOCUMENT_ from the user's point of view, that's best. If not, it
would be better to dispense with the document model.
AP> - in many cases, the output data are just the result of some
AP> calculation, and may be stored as plain text files. Sometimes,
AP> however, new spectra are created
AP> by manipulating existing ones, and must be archived on disk.
This looks to me rather like the latter (no document structure case).
AP> but I don't find the solution appealing, because the
AP> application should read/write/keep in [virtual] memory a large amount of
AP> unused data.
What's "large"? If megabytes or less, quite all right.
AP> After all, I've started programming in the early '70, when
AP> 32Kbytes were a dream, and economy has become a second nature...
Yeah. Where are the times we xored a register to itself, since it was faster
and a byte shorter than to zero it ;)))
Incidentally, do consider using property lists (structures made from
NSStrings, NSArrays, NSDcitionaries, NSSets, NSNumbers) for the data.
Suprisingly often it means simpler, and thus easier to make, debug, and
maintain code, than preparing specific classes.
---
Ondra Cada
OCSoftware: email@hidden
http://www.ocs.cz
private email@hidden
http://www.ocs.cz/oc