Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Strategy to split up large class files?

On Jun 30, 2004, at 13:29, Andreas Mayer wrote:

Am 30.06.2004 um 13:08 schrieb Arthur Clemens:

Is there a strategy to split up my AppController class in smaller chunks (separate class files that belong to AppController perhaps)?

If you just want to distribute the code to different files you can use categories.

But 80 methods seem to be a lot for a single class. I'd think about moving some functionality to separate classes.

The problem I have is that each part has some relation to the interface. If I separate the registration part to a category, the IBAction methods are not accessible in Interface Builder (or should I leave the declarations in the AppController.h? - this seems to get messy).

So I could move registration to a separate class, including IBAction methods. Then I need to instantiate the Registration class in Interface Builder. And in AppController, I would need to change oRegistrationWindow to [mRegistration window]. Is this the way to go?

Arthur
_______________________________________________
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.

References: 
 >Strategy to split up large class files? (From: Arthur Clemens <email@hidden>)
 >Re: Strategy to split up large class files? (From: Andreas Mayer <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.