Re: Tracing an iPhone application/framework
Re: Tracing an iPhone application/framework
- Subject: Re: Tracing an iPhone application/framework
- From: Andy Lee <email@hidden>
- Date: Tue, 19 Oct 2010 08:57:49 -0400
On Oct 18, 2010, at 11:38 PM, Sandro Noël wrote:
> The "framework" is built as a template application from which classe/functions can be overloaded to fit the needs of the being built application.
> not much of an architecture if you ask me but i have to document it none the less.
Isn't that what a framework is? A bunch of classes whose methods are intended to be overridden?
Anyway -- as a user of a framework, if I understand what functionality a class is supposed to encapsulate, and the purpose of each of its public methods, I usually shouldn't care which methods call which other methods. That's an implementation detail, though sometimes it *is* useful and even important to know.
When diving into a body of code I didn't write, I sometimes find it a challenge to see the big picture. The last time I did this I wish I had thought to look at the class hierarchy in Xcode using Project -> Class Browser. You can tell it to only show your project's classes. Protocols and categories are also listed. Maybe that would help in your situation?
--Andy
_______________________________________________
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