On 5/31/05 9:08 PM, ZhaoYu didst favor us with:
>> For Tiger and later, your best bet is probably to replace that code
>> with CGBitmapContextCreate and the image import routines in Image I/O.
>>
>
> Well, how about to develop a software can run on all MacOS X 10.1/2/3/4? Maybe
> we need a abstract layer to encapsulate QuickDraw and Quatz, QuickTime and
> Image I/O? Oh, so many things have to do. Why Apple didn't provide a
> consistent, back compatible API? Or Apple wish our software just sold to who
> has Tiger? Sorry, I know there are so many COOL features in Tiger, but I have
> to still use older API to let our software can run on 10.1.
Why? Almost no one uses 10.1. !0.2 was the first release many considered
useable, and this is what I saw: When 10.1 was released, people dropped
support for 10.0 almost immediately. When 10.2 came out, people dropped
support for 10.1 almost as fast as they dropped support for 10.0. But when
Panther was released, we didn't see that with 10.2. Many developers
continued to support 10.2 and still support it even now. But almost no one
supports 10.1 anymore. I suspect one of the reasons is that Apple pushes
composiited windows as the future of Mac OS X and 10.1 doesn't support
composiited windows, so that can really limit you if you're trying to
support 10.1. Why do you need to support 10.1?
Larry
_______________________________________________
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
