Re: Document App or not?
Re: Document App or not?
- Subject: Re: Document App or not?
- From: mmalcolm crawford <email@hidden>
- Date: Sun, 8 Feb 2004 13:22:53 -0800
On Feb 8, 2004, at 12:07 PM, email@hidden wrote:
Multiple instances are really a good indicator, but personally I choose
Document based apps if I find myself writing a controller and an object
that is either instanciated (?sp god my spelling is horrid) by the
controller, or the object passes data to controllers for the view and
the
main control and never really "does" anything on it's own except act
as a
data storage bin for what the user is doing. (isn't that the
definition of
a document?)
Just for clarification -- the controller should be a controller, it
should manage model objects. It shouldn't be a "data storage bin" per
se.
As for "document-based applications"; the documentation states:
"In the context of the Application Kit, a document is an instance of a
custom NSDocument subclass that knows how to represent internally, in
one or more formats, the persistent data displayed in windows. A
document can read that data from files and write it to files."
<
http://developer.apple.com/documentation/Cocoa/Conceptual/Documents/
Concepts/WhatIsADocument.html>
Certainly you can use the document architecture for other ends, however
the less your application is conceptually "file based" the greater the
likelihood that you will be working against, rather than with, the
system.
mmalc
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.