Re: IB action connections and classes implemented across several files
Re: IB action connections and classes implemented across several files
- Subject: Re: IB action connections and classes implemented across several files
- From: Antonio Nunes <email@hidden>
- Date: Sat, 11 Apr 2009 18:29:58 +0200
On 11 Apr 2009, at 17:50, Kevin Cathey wrote:
You can still have a single header file. For each category of
methods, you would create another @interface block. [...]
Then, you would have the implementation files, one for each of your
@interface blocks
Interface Builder will then read your MyClass.h and you will have
all of your instance variables and actions for the entire class.
That's what I did, but I still got the warnings. It would seem the
system doesn't look at categories on a class when looking for
declarations of the connected selectors, even if they are in the same
header file as the class itself.
That said, if your classes are getting so large that you have to put
them in separate files, that might be an indication of some
refactoring you can do. Check out Martin Fowler's Refactoring book
to see what refactorings you can apply to "large classes".
Thanks, I wasn't aware of that book. I checked it out online and will
probably order it once I'm back home next week. I've been meaning to
put in a period of time for refactoring the project anyway. I'll take
your communication as a sign it is high time for that. :-)
António
----------------------------------------------------
Disapprove of sin but not of the sinner
----------------------------------------------------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden