Re: NSDocument as controller vs. as model
Re: NSDocument as controller vs. as model
- Subject: Re: NSDocument as controller vs. as model
- From: Stefan Jung <email@hidden>
- Date: Mon, 1 Oct 2001 10:49:41 +0200
NSDocument is a controller. Of course you add model functionality to it.
In simple cases this may be appropriate, but if your program grows,
especially if you support more filetypes, then i will become more and
more complicate to maintain your code. At least NSDocument is never ONLY
the model. The naming is confusing as there is an additional
NSDocumentController class, but NSDocument is meant to be a controller.
Stefan Jung
I've seen a couple different examples of a document based application
under Cocoa. In some examples I see "NSDocument is the model", whereas
in other examples I NSDocument as a controller to the model (model vs.
model-controller").
Is this just a stylistic thing or is one way "more correct than the
other"?
Thanks,
Brian
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev