Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CG vs QuickDraw



On Sun, 10 Jun 2007 23:04:04, Ingemar Ragnemalm <email@hidden>
wrote:

> David Duncan wrote:
>> On Jun 10, 2007, at 09:31 AM, Ingemar Ragnemalm wrote:
>> 
>>> Transparency, anti-aliasing: Not really an issue, QuickDraw does them
>>> pretty well.
>> 
>> Quickdraw only really understands binary transparency (regions). It
>> only anti-aliases text (and not as well as Quartz). Quartz natively
>> understands full alpha transparency and can anti-alias everything.

To extent, QuickDraw was as (or even more) powerful in transparency
than Quartz is. CopyMask allowed per pixel per color component
alpha transparency! Granted, CopyMask drawing wasn't recorded in
pictures, but I remember I've created a couple of truly transparent
picts: one was using QuickTime's stdpix bottleneck (the resulting
pict was rendered quickly), the other was a hack, that used pure QD
drawing without QuickTime embedded (basically it drew each pixel
separately with the proper OpColor set and blend transfer mode,
the rendering speed was pure). If anyone interested I could email
those picts (will take me a few days to find them). CopyMask aside,
plain primitives (rects, regions, etc) could also been drawn with
blend mode - per color component alpha transparency.

>>> Loading pictures: Much easier in QuickDraw.
>> 
>> Have you looked into Image I/O? You can load most of the common image
>> formats in 2 function calls: CGImageSourceCreateWith[Data |
>> DataProvider | URL]() followed by CGImageSourceCreateImageAtIndex().
>> Granted, this is only 10.4 or later.

Well, this is not strictly Quartz or QuickDraw issue, but look,
in past we could specify picture ID in DITLs/CNTLs directly, no
extra code was required at all, not even a single line. We can't
do this now in Carbon nibs.
 
> On more thing: QD Bottlenecks. (Could have been a subject of its own.)

Yes, I miss bottlenecks. Along with picture comments.

Some other things, from the top of my head:

- As we saw recently there are no easy ways (as of 10.4) to create
shapes (regions of new era) from polygons, paths and bitmaps.

- no easy way to mimic QD clipping handling with Quartz code (not
necessarily bad for Quartz, just a major difference).

- there was no such a thing in QuickDraw, but I naively thought
it will be in Quartz, but it is not: ability to represent
arbitrary images (vector, bitmap, different formats, drawing proc)
by a "ref". CGImageRef is not such a thing. CGPatternRef is closer,
but...for patterns and doesn't support image files directly.
NSImage is still closer but that's not Quartz.
[Alternatively, the same could be achieved by having "drawProc"+
"userData" as one of the options in HIViewContentInfo and similar
structures.]

- Debugging CGContextRef and contexts stack. rdar://4664063
(viewing context's contents' for debugging purposes).

Mike
[Author of the exclusive "QuickDraw 20-th anniversary" t-shirt.]
[Hey, Joseph, we are discussing QuickDraw here!]


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden

This email sent to email@hidden

References: 
 >Re: CG vs QuickDraw (From: Ingemar Ragnemalm <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.