|
|
Objective C
|
|
|
|
Fresh-Faced Recruit
Join Date: Jun 2000
Status:
Offline
|
|
I have been trying to work with Interface Builder and Project Builder to create some basic programs in OS X and I am finding that I need to learn more about Objective C. I know C++ and so I can sort of read Objective C and my program can execute tasks when I click on buttons. I am now am trying to create more complicated and useful functionality. I have read the documentation I could find on Apple's web site about Objective C and found it lacking in substance (disclaimer: or myself lacking in brains.) Does anyone know of any good books or better yet know of some good places to find sample code? I have looked at the sample code that is included on the OS X DP4 install and it doesn't cover samples of what I am trying to figure out. For example I am trying to create a list view that shows the file names that I have searched for and I was not able to make sense of Apple's documentation about datasources. It just felt like they assumed some information that wasn't transparent to me. Any helpful programmer links or books etc... for Objective C and OS X would be greatly appreciated. Deep peace to you.
-Brian
|
|
|
|
|
|
|
|
|
ralph_on_dp4
|
|
try http://www.stepwise.com
They have some sample code and further infos, most of it is still related to MacOS X Server + Openstep, but that's where Objective C comes from.
You might also try to get some old OpenStep manuals...
PS: Apple recommends programming the Cocoa APIs in Java...
Hope that helps.
Ralph
|
|
|
|
|
|
|
|
|
Michaeld
|
|
Sorry...but they don't,
At the Cocoa seminars at WWDC, they were recommending using Objective C, and saying that Java is there...but not completely. IE Java will work, but still has some developement to do.
Cocoa is made of Obj C, and this OC will, for the time being, work the best in it.
Mike
PS: Apple recommends programming the Cocoa APIs in Java...
Ralph
|
|
|
|
|
|
|
|
|
ralph_sch
|
|
Hi Mike,
I really haven't been to WWDC myself, but after reading Jobs' JavaONE statements and the announcement of a Java version of WO I really thought Apple might prefer Java for Cocoa, too. I have just played around a bit with DP4 but I'm really closer to WO than to what Cocoa is going to be on MacOS X. I haven't spent a lot of time with DP4 because I heard that WO 4.5 apps are not going to be supported on this platform. However, I do not know too much about what Cocoa is going to be, but I really think if Apple is going to carry on with their Objective C support, Java will be supported at least equally because there are a * lot * more people dealing with it and Apple really needs support for the platform.
Currently, WO and the Yellow Box (whatever it may be called next week) are one, but I have absolutely no clue where EOF is going... I really don't want to be some sort of smartass here, so if you have more info on this topic, I should be grateful if you could enlighten me further...
Ralph
|
|
|
|
|
|
|
|
|
bentwookie
|
|
When I first started Cocoa programming a year ago, I thought, "I really don't want to learn a new language, much less one used by only one company." Well it's a year later, and I can't describe how much I love ObjectiveC.
If all you've ever known is C/C++, you owe it to yourself to see how nice OO can be. Beyond being OO, it is EXTREMELY dynamic.
For example, "pointers" to functions (although I hesitate calling them pointers) can be described and stored easily using the @selector command. When you make connections in InterfaceBuilder, it's just storing these selectors to use later at runtime. You simply cannot do this with a static language like C++.
Look at MFC. Applications created with it are a mess of macros and VisC++ generated code. We've all had this system come crashing down at one time or another because somebody checked in a bogus .h file or incorrectly tweaked a //AFX<messofcraphere> insertion. It doesn't work! IB and ObjectiveC do!
The AppKit and Foundation frameworks were built in ObjectiveC. As such, you'll have a better time using them in ObjectiveC.
Short of learning a new language (and it's sooo simple to pick up), what's the point of using Java? You're linking against the AppKit anyway, so your end result isn't 100% Java. It's just slow.
|
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Jan 2000
Status:
Offline
|
|
I know C and used C++ enough to know I never want to touch it again. Objective-C looked very cool. I read though the stuff at Apple developer site and felt I could pick it up rather quickly. It's worth reading the intro over there. I think there's sample code too?
|
|
|
|
|
|
|
|
|
Fresh-Faced Recruit
Join Date: Jun 2000
Location: PORDENONE, PN, Italy
Status:
Offline
|
|
|
|
|
|
|
|
|
|
|
Michaeld
|
|
Hi Ralph
You are absolutely right about Apples total commitment to Java. They want OS X to be the premier Java developement and deployment machine.
Its just at the moment Apple is working on bringing full Java support to Cocoa. They are close to it, but not quite there yet. Thus there comments at WWDC to also check out Obj C.
Also...remember the audiances they were preaching to. At the seminar at the WWDC they were mainly NeXt Developers there, while at the Java conference...well, you guess who was there ;-).
As far as I am aware...Apple will keep up Obj C for the Next ppl, and Java for Sun and everyone else.
I think Apple's long term path is pretty clear. Classic will die soon (or be put to the back of the priority queue), they will encourage developers to phase out of Carbon and into Cocoa with either Java or Obj C, and Java and Obj C will be the languages of the future.
Mike
Originally posted by ralph_sch:
Hi Mike,
I really haven't been to WWDC myself, but after reading Jobs' JavaONE statements and the announcement of a Java version of WO I really thought Apple might prefer Java for Cocoa, too. I have just played around a bit with DP4 but I'm really closer to WO than to what Cocoa is going to be on MacOS X. I haven't spent a lot of time with DP4 because I heard that WO 4.5 apps are not going to be supported on this platform. However, I do not know too much about what Cocoa is going to be, but I really think if Apple is going to carry on with their Objective C support, Java will be supported at least equally because there are a * lot * more people dealing with it and Apple really needs support for the platform.
Currently, WO and the Yellow Box (whatever it may be called next week) are one, but I have absolutely no clue where EOF is going... I really don't want to be some sort of smartass here, so if you have more info on this topic, I should be grateful if you could enlighten me further...
Ralph
|
|
|
|
|
|
|
|
|
Forum Regular
Join Date: Mar 2000
Status:
Offline
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Forum Rules
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|