Re: What framework & language is good for an old C++ mule.
Re: What framework & language is good for an old C++ mule.
- Subject: Re: What framework & language is good for an old C++ mule.
- From: Uli Kusterer <email@hidden>
- Date: Mon, 13 Mar 2006 02:46:08 +0100
Am 13.03.2006 um 00:02 schrieb cudrnak:
I really don't want to go down rant road, but I am put off by the
objectionable-C syntax because, to my C/C++ trained eyes, many
things seems like odd ways to define things.
It takes some getting used to, but just like C++'s syntax for the
"for" command or templates, it's something you'll get used to after a
while.
Can anyone suggest a good route for me? Would I have a shorter
learning curve with cocoa/Java?
Apple recently announced that Cocoa/Java will not be continued. It
is not going away, but the new APIs won't be bridged to Java anymore.
So, if you are just doing this as a hobby on an old Mac, go with
Cocoa/Java, but if you want to sell or upgrade to new Macs and use
new features, it's not the way to go.
Would CodeWarrior/PowerPlant be a better choice because of my C/C++
background?
CodeWarrior will not be ported to run on Intel Macs. Like above,
this could be a problem for you.
Personal experience or even just pointers to existing web pages
would be great.
My recommendation is Cocoa. But that's not surprising as this is
the Cocoa-Dev mailing list. If you want a second opinion, ask your
question on Carbon-Dev as well, and maybe on OmniGroup's MacOSX-Dev
list as well (might get some AppleScript or OCaml folks etc. there
who might be more objective).
Anyway, to learn Cocoa, the best option is to get Aaron Hillegass'
book on Mac OS X programming. I'm an old C++er myself, and it took me
a weekend to work through the book and learn how to use Cocoa. So,
it's easy. You may want to also read Apple's book on the ObjC
language to fill in some blanks (like what categories are -- at least
the 1st edition of Hillegass didn't really explain that).
Of course it'll take a little longer to get rid of some C++isms one
tends to do, but it's okay.
Carbon is a good API if you want to go low-level, but for GUIs
you'll find yourself doing way too much work, and its pseudo-OO
syntax really causes problems when trying to wrap it in your own C++
class library. I wouldn't recommend it if you want to code OO. If you
find some cool feature in Carbon that isn't available in Cocoa, you
can usually mix the two, and if you need to interface to a cross-
platform C++ codebase, you can do that with Objective C++ (which is a
way to use both languages in a single ".mm" file).
Cheers,
-- M. Uli Kusterer
http://www.zathras.de
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden