Re: Dealing with exceptions in a drawing stack
Re: Dealing with exceptions in a drawing stack
- Subject: Re: Dealing with exceptions in a drawing stack
- From: Paul Bruneau <email@hidden>
- Date: Mon, 19 Jan 2009 12:57:47 -0500
On Jan 19, 2009, at 2:49 AM, Kyle Sluder wrote:
3) You've over-architected your drawing code. Typically the fewer
objects that are responsible for drawing (i.e. view objects) the
better. Situations like the one you're describing often arise from
making model objects responsible for their own drawing.
I was a little disappointed that Graham didn't address this point.
I'm confused by it, since I have been directed in the past by people
who know that The Cocoa Way is to have objects know how to draw
themselves--via a category if desired.
Is there differing opinion on this? (apparently there is...)
I am going to be starting a large app that will have many assemblies
and sub-assemblies that I want to draw. I had planned on the objects
drawing themselves. Should I revisit my thinking?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden