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: What Should I learn Before Cocoa?

I will look into Cocoa Programming for myself. Granted, I haven't felt any real compelling need to develop a program for the Mac, and my day job has turned to developing for Windows for a couple more weeks.

However, I still look at some of the code in Objective-C and compare it to C++ and wonder why the function calls in Objective C are so dang long. I don't know of another language where you specify the function's variable along with the passing variable.. :)

That, and I think PB could be updated to ease the transition, like function completion on objects and doing other automated functions that modern IDE include.. I haven't seen XCode, so I can't comment, however I think some things have been addressed in XCode... or at least I hope so... can't wait to download it..

Thomas
On Thursday, September 4, 2003, at 10:49 AM, Mitch Chapman wrote:

On Thursday, September 4, 2003, at 09:20 AM, Thomas McQuitty wrote:
What I really need is a conversion manual from Dev Studio to Project Builder/Interface Builder.

I understand the MVC philosophy, however, I am still a little slow in the learning how to implement it with PB/IB (Outlets and Actions) rather than a more connected method of development (DevStudio). Then again, it could just be that I have spent so much time in the MFC environment, much of it comes naturally now.. Who knows....

I come from a background of DevStudio, Borland Delphi, and pygtk/libglade.
I haven't had so much trouble with PB/IB per se, but it has taken 10 months
(granted, on my own time) to begin feeling comfortable with Cocoa.

You said it very well: I understand MVC, but am slow in figuring out
how familiar patterns are implemented in Cocoa. Maybe part of the
problem is that Cocoa offers more "recommended" ways of connecting software
entities to each other, and it's hard to figure out when each technique
is appropriate.

For example, years ago I implemented Callback and Observer components
in Python. The interfaces were simple, and the range of uses broad.

Cocoa provides several mechanisms -- the target/action paradigm,
NSNotificationCenter, informal delegate protocols which define "custom
adapters" for some types of notification -- to cover the same situations.
The interfaces for these mechanisms are comparatively "thick"; there's
more stuff to call. So it has been difficult to figure out which
mechanisms to use in which circumstances.

Anyway, to get back (or at least closer) to the thread, I'm _finally_
becoming comfortable enough with Cocoa to find "Cocoa Programming"
(Anguish, Buck, Yacktman) both understandable and interesting.
So after you've read some of the books on Objective-C and something
like "Building Cocoa Applications with Objective-C", you might want
to pick up a copy of "Cocoa Programming".

--
Mitch
_______________________________________________
projectbuilder-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/projectbuilder-users
Do not post admin requests to the list. They will be ignored.
_______________________________________________
projectbuilder-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/projectbuilder-users
Do not post admin requests to the list. They will be ignored.
References: 
 >Re: What Should I learn Before Cocoa? (From: Mitch Chapman <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.