 |
 |
CodeWarrior vs Project Builder
|
|
|
|
|
Dedicated MacNNer
Join Date: Feb 2001
Location: Buenos Aires, Argentina
Status:
Offline
|
|
I was told that to program in C++ it's better to think using CodeWarrior. Especially if the code has to be ported to the wintel platform.
is it true?
Or better stick to Project Builder and Obj-C?
thanks
N
|
|
iMac 1GHz 17" Super Drive
iPod 5GB
|
| |
|
|
|
|
|
|
|
Forum Regular
Join Date: Oct 2001
Location: Sweden
Status:
Offline
|
|
When it comes to GUI programming, there's nothing like Cocoa, it absolutely rocks. If you need to go cross platform I'd recommend you implement your core logic in C and/or C++. Then you can build your platform specific code on top of that, it's easy to integrate ObjC code with existing C/C++ code. For Windows you might build your GUI in Visual Studio or whatever. You could develop your core logic using either CodeWarrior och Project Builder. I haven't done much C++ programming in PB, but I guess it's ok. You might find CodeWarrior better for C++, but on the other hand it's not free.
|
|
|
| |
|
|
|
|
|
|
|
Dedicated MacNNer
Join Date: Nov 2000
Location: Malaysia
Status:
Offline
|
|
Originally posted by Mac_Nacho:
I was told that to program in C++ it's better to think using CodeWarrior. Especially if the code has to be ported to the wintel platform.
is it true?
Or better stick to Project Builder and Obj-C?
thanks
N
I do very little C++ coding, but there is nothing stopping you from using PB for C++. I do not want to start the flames a-going, but IMHO CodeWarrior is a good tool, but it is especially well known by "legacy" mac developers. But there is nothing that says "C++ is done in CW". The legacy devs love it--and it is supposed to be much faster than PB. But XCode is coming out that is an attempt to be a CW-killer.
If you've never used CW, but want to program in C++, I would start with PB no matter what--it costs you nothing. If you get to a point that you really need to do things PB does not have, then upgrade to CW.
About OjbC vs. C++, there has obviously been a lot of discussion on this topic. I used to be all "ObjC is the only way to go". It is a kewl language. But at this years WWDC, there was a LOT of talk from Apple about C++. Even though they buried OS9 last year, C++ is a *BIG* part of the development environment and is in most cases just as fast as ObjC in OSX. It will always be a part of Apple's OSes for the foreseeable future. (I mean GCC handles it out of the box).
---gralem
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Sep 2000
Location: Norfolk, Va
Status:
Offline
|
|
That said, and harboring no feelings that developers should all use ObjC, ObjC will always be the language of the OS for OS X.
So to be truly like an extension of Cocoa ObjC is it. Not that that should be what makes a person decide the way to go.
Anyway. what I really wanted to ask was, for CW people, how do you create GUIs?
When I got CW academic 2 years ago it sucked so bad (read: I couldn't figure out how to make text appear in a window, and all the tutorials were for this "hell world" CLI crap) that I quit programming until this year.
|
|
you are not your signature
|
| |
|
|
|
|
|
|
|
Dedicated MacNNer
Join Date: Jan 2001
Location: Boulder, CO, USA
Status:
Offline
|
|
Originally posted by Gametes:
That said, and harboring no feelings that developers should all use ObjC, ObjC will always be the language of the OS for OS X.
So to be truly like an extension of Cocoa ObjC is it. Not that that should be what makes a person decide the way to go.
Anyway. what I really wanted to ask was, for CW people, how do you create GUIs?
When I got CW academic 2 years ago it sucked so bad (read: I couldn't figure out how to make text appear in a window, and all the tutorials were for this "hell world" CLI crap) that I quit programming until this year.
LOL.  The old-fashioned way, to be sure.
Actually, you can use interface builder bundles in C/C++ carbon apps without too much pain. Otherwise, and particularly for older apps, it's the old resource fork or some home-grown version of it. The latter, of course, if you need cross-platform agony -- uh, I mean bliss.
Also lots of folks adopted PowerPlant, a Metrowerks C++ framework, which had Constructor, a view editor along the lines of IB, but not as flashy.
As for the question ... I love Codewarrior and will mourn its passing greatly. I use CW on Mac and Visual Studio on Windows and when I need to actually get work done, even if it's windows-specific code, I use CW.
|
|
|
| |
|
|
|
|
|
|
|
Dedicated MacNNer
Join Date: Jan 2001
Location: Boulder, CO, USA
Status:
Offline
|
|
Oh right. One thing: CW's code completion is not so great. 
|
|
|
| |
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Mar 2000
Location: London, UK
Status:
Offline
|
|
Originally posted by Gametes:
ObjC will always be the language of the OS for OS X.
What exactly are you on about? Most of the actual OS itself isn't written in Obj-C, only the apps.
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Sep 2000
Location: Norfolk, Va
Status:
Offline
|
|
And the entire Cocoa framework, right?
|
|
you are not your signature
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
Top