2007-11-25
Subscribe to:
Post Comments (Atom)
Blog Archive
Labels
- programming (18)
- bug (8)
- faq (7)
- gcc (5)
- rant (4)
- coregraphics (3)
- opengl (3)
- psa (3)
- quicktime (3)
- idevgames (2)
- imageio (2)
- languages (2)
- launchservices (2)
- philosophy (2)
- apology (1)
- autotools (1)
- c++ (1)
- codesign (1)
- corevideo (1)
- createmacgames (1)
- curl (1)
- cwd (1)
- delicious monster (1)
- downtime (1)
- dynamic linking (1)
- files (1)
- games (1)
- ghc (1)
- glsl (1)
- glut (1)
- ichat (1)
- install_name (1)
- intel (1)
- kiloplane (1)
- leopard (1)
- limerick (1)
- random (1)
- ruby (1)
- scons (1)
- textmate (1)
- threading (1)
- tutorial (1)
- universal binary (1)
- usability (1)
- x3100 (1)
- xcode (1)
5 comments:
Ouch.
Still, consider the source. At least he’s taking some sort of positive action, even if it’s in the wrong direction.
</snark>
Well, if we can't use Carbon for games, then how can we code cross platform games?
The reason that I use Carbon is because a large amount of the code can be reused on Windows and Linux.
Without Carbon support I would have to use Cocoa, thereby relegating all the code to be Mac only.
Is there a way to still share the main C++ code base with Windows/Linux while using a small amount of Cocoa code?
I can't use Objective-C to code games, then need to be able to run on other platforms.
I can't use Objective-C to code games, then need to be able to run on other platforms.
Oh boy - is Apple trying to make it hard for people to cross-code? (possible end-result: fewer apps made for both Mac and Windows?)
I can sort of understand the reasoning behind the Carbon decision (that I know of, which is almost nothing) - it's a pain to maintain two sets of APIs, and there are some things that are accessible only in Carbon that Cocoa programmers would really like a "built-in" object-based interface to - or there was I forget what it was, but it may have been migrated over.
My original impression however, was that Cocoa objects were mainly wrappers that made calls to Carbon (or Foundation) routines. Is this no longer true, or is Apple just not going to expose the "underneath layer" anymore?
As for Quesa - I have no real comment. I looked at it a bit (about 5 or 6 years ago). My understanding was that - like QD3D, it was built for doing higher level things that OGL was (at the time). But OGL has evolved quite a bit from then..
AARGH - Is there is no way in Blogger to log-in for the first time, post a comment, AND select "email follow-up.." at the same time? (Hence the deleted comment above..)
Objective C, C and C++ can be freely intermixed. Using Cocoa does not in any way prevent you from writing a cross-platform application.
The Mac OS X version of SDL uses Cocoa, while presenting the same cross-platform C API, for example.
The Mac OS X port of Quake 3 uses Cocoa, while sharing the entire game codebase with Windows and Linux.
Post a Comment