Wrox Programmer Forums
|
BOOK: Beginning Mac OS X Programming
This is the forum to discuss the Wrox book Beginning Mac OS X Programming by Michael Trent, Drew McCormack; ISBN: 9780764573996
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Beginning Mac OS X Programming section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old June 27th, 2009, 06:38 PM
Registered User
 
Join Date: Jun 2009
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default Subclassing

Hey all,

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.

Thanks in advance for any help or suggestions.





Similar Threads
Thread Thread Starter Forum Replies Last Post
Subclassing system.web.ui.page gazeth BOOK: ASP.NET Website Programming Problem-Design-Solution 2 May 25th, 2004 10:02 AM
Subclassing...Help Please! gede Pro VB 6 1 March 29th, 2004 09:53 AM
Subclassing HuhOiC C# 0 June 4th, 2003 03:12 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.