Re: Mac OS X 10.1 File Name Extension Guidelines
Re: Mac OS X 10.1 File Name Extension Guidelines
- Subject: Re: Mac OS X 10.1 File Name Extension Guidelines
- From: Lloyd Sargent <email@hidden>
- Date: Tue, 11 Sep 2001 09:34:59 -0500
On Tuesday, September 11, 2001, at 02:52 AM, Ondra Cada wrote:
John,
John C. Randolph (JCR) wrote at Mon, 10 Sep 2001 23:26:26 -0700:
JCR> Within each app we have objects, and they act in
JCR> various ways, but at the top level of the system we're still
essentially
JCR> working procedurally.
...
JCR> What if we didn't need TextEdit.app, because simply loading an
NSText
JCR> object into memory would suffice? (Every object its own app, using
or
JCR> not using the framework code as appropriate?)
Don't want to sound like a spoilsport, but I guess when such a design is
finished, it would became obvious that they just reinvented SmallTalk ;)
I thought that was the job of the next generation - to re-invent what
the previous generation already invented <grin>.
I like the object idea, but it boils down to how you use it. In other
words there are hammers and there are nails and both serve a vital
purpose. Neither role can be reversed. To argue that they both should be
considered equally works in the abstract, but not in the concrete (or
the wood). Granted the sniffer concept I like (albeit I fear there are
too many exceptions to the rule at this point).
I dunno, have we reached the point of no return, or can the genie be
stuffed back into the bottle? Do I ALWAYS what a JPEG to be opened by
the same application (if I have Photoshop and PixelMaster and the both
create JPEGS will they be opened by their respective programs or am I
stuck with one or the other?).
Rock or hard place?
Cheers,
Lloyd
--------
Canna Software Development
"Llamas generally avoid mailing lists, primarily because it strains
their eyes."