Re: Potential O'Reilly Cocoa books (was Docs)
Re: Potential O'Reilly Cocoa books (was Docs)
- Subject: Re: Potential O'Reilly Cocoa books (was Docs)
- From: Chris Gehlker <email@hidden>
- Date: Thu, 23 Aug 2001 08:09:12 -0700
On 8/23/01 7:46 AM, "Ken Tabb" <email@hidden> wrote:
>
As a side issue, there is very little Cocoa API for things like QuickTime
>
and OpenGL... you're basically given an NSMovieView or NSOpenGLView in
>
which to show your stuff onscreen, which gives you programmatically a way
>
of getting to (Carbon, not Cocoa) Movie structures or AGL structures. But
>
at the end of the day you're left doing Carbon API programming in a Cocoa
>
app. Clearly this presents a learning curve for Cocoa (or Object
>
Oriented) programmers, who may never have touched Carbon (or procedural
>
programming) before... neither the Carbon QuickTime API nor the Carbon
>
OpenGL / AGL API is object-oriented (this is so that C programmers can
>
use it). As such, the docs for NSMovie and NSMovieView assume you're
>
already familiar with QuickTime coding using Carbon, in a sort of "and
>
there you go, there's your carbon Movie structure complete with GWorlds"
>
manner... if that's the case, why would we be using Cocoa etc.?!! Maybe
>
this will all change in 10.1 (haven't received the beta yet), who knows?
I'm afraid it's not going to change at all. QuickTime is, mostly, portable
to Windows and really old versions of MOS. It even builds in the old Mac
memory manager stuff on Windows. I can't really see Apple breaking the
portability so I think it will stay straight C.
Even for Cocoa programmers QT is just this thing sitting off by itself. It's
Pascal roots really show.
AFAIK, the situation with OpenGL is pretty much the same except it doesn't
address memory management and Apple doesn't control the API.
--
In the midst of great joy, do not promise anyone anything. In the midst of
great anger, do not answer anyone's letter. -Chinese proverb