>        Just FYI, Carbonizing turned out to be a much more invasive
>        procedure than we had expected, and I'm sure we got off easy
>        because the Mac version of MetaCard wasn't done all that long ago.
>        I'd guess that Carbonizing some of those older apps out there is
>        going to be a real challenge and so it'll probably be a long time
>        before most people will be able to stop using the compatibility
>        box (aka Classic).

That's a very true statement, although I've been extremely impressed by how 
many of the programs that I do use on a regular basis (Mulberry, 
GraphicConverter, IE/Netscape, QuickTime, DropDrawers, etc.) do already 
have Classic versions out the door. I also find myself easily getting by 
without Classic right now, except for that urge to use MetaCard. :)

>        This is not a very accurate description of the issues.  We're not
>        planning a port to the "native" drawing system on OS X (Quartz),
>        but instead to Carbon, a subset of the current Mac OS APIs.
>        Quartz by itself is not developed enough to use directly, so you
>        have to use one of the two higher-level APIs for it.  There will
>        be very few new apps that will use the other high-level API
>        (Cocoa) which is based on the old NeXTStep APIs because most
>        developers are smart enough to see the handwriting on the wall
>        about the eventual phase out of that API.  The only exception may
>        be the poor Java developers for whom Cocoa represents yet another
>        unavoidable set of proprietary extensions they'll have to deal
>        with.

As I work for Apple, I know Apple originally intended to push extremely 
hard for Cocoa vs. Carbon, since Apple (aka NeXT) firmly believed in its 
vast superiority. For those of you who may have had a chance to program for 
Cocoa, you may agree, as do I, it's incredible. (Maybe not as incredible as 
MetaCard, but hey, that's expected :) Internally Apple still strongly feels 
a need to push Cocoa, but marketing-wise Apple just saw it as something 
that would confuse and turn away developers. I'm doubting it will die away 
quite as rapidly as Scott may have eluded to here as the majority of what 
Apple has written is still Cocoa (excluding the port of AppleWorks).

Anyways, like everyone else, I'm eagerly waiting (like a kid in a candy 
store) the version of MetaCard that runs on Mac OS X. And knowing Scott and 
the MetaCard I use today, it will have it's quirks, but will be incredible.

Reed

Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.

Reply via email to