You are currently viewing the BOOK: Beginning Mac OS X Programming section of the Wrox p2p Programmer to Programmer discussion community. This is a community of more than 40,000 computer programmers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining our free Wrox p2p community you can post your own programming questions and respond to other programmers’ questions. Registered users also don't have to see the ads that are displayed to guests. Registration is fast, simple and absolutely free so please, join today!
Join today and post to win prizes! Post more to increase your chances of being Wrox’s top poster of the month.
Hope you are all doing well. I have a question (coming from a .NET background). I noticed that with the example application they did a whole lot of subclassing for the different image window objects.
I am just trying to find out if this is really necessary? I don't understand why you would have to subclass the MyDocument.nib file just to add the mImage variable and an accessor. I know there were probably more pieces of code in the implementation, but all that seems like it would be just fine placed in the original MyDocument.nib file.
What am I missing? I thought that maybe this was just done to prove the point that you CAN do it, and how to do it when you need to. I would love to receive any information from some Cocoa developers out there. The move from .NET is proving to be pretty difficult.
Subclassing
Linear Mode
