Re: ScreenSaverView/NSQuickDrawView/Opaque issue [update]
Re: ScreenSaverView/NSQuickDrawView/Opaque issue [update]
- Subject: Re: ScreenSaverView/NSQuickDrawView/Opaque issue [update]
- From: glenn andreas <email@hidden>
- Date: Fri, 3 Jun 2005 10:35:31 -0500
On Jun 3, 2005, at 10:14 AM, Andy O'Meara wrote:
Hmm, interesting. The developer part of me is happy that something
like
CoreVideo can address my needs, however, the part of me that has to
tell my
mac os customers they need to upgrade to tiger is very concerned.
I'd have
a lot less of a problem a year from now, but to require it now is a
heartbreaker, especially for something just like a screensaver. So in
summary, thanks for the CoreVideo recommendation--I'll have to get
into
that, but I can't require Tiger just yet...
According to the docs:
Mac OS X v10.3 when QuickTime 7.0 or later is installed
So you can just tell people to upgrade to QuickTime 7.0, which seems
like a fair compromise (between QT 7.0 and the various updates in
10.3.9 such as WebKit, it's actually surprising how much "Tiger Only"
stuff is actually available under 10.3).
That said, thanks for your time and assistance with this. If you
or anyone
here has any further insight into the three questions/issues I
posed a few
messages ago, that'd be great too.
The best I can offer is "NSQuickDrawView is a temporary transition
tool built on top of currently deprecated software and will probably
be deprecated itself real soon now". Sorry.
I guess what kills me is that the source to the AppKit classes isn't
publicly available, causing non-cocoa gurus (like me) to be
discouraged by
having to play guess-and-check all day (the standard practice for
Win32 and
MFC development)--at this point, pretty dispirited with regard
Cocoa. Would
Apple stand to lose anything from making the core NS* classes source
publicly available? The answer seems to be no, but perhaps I'm wrong.
Not wanting to start a big OT philosophical debate, yes, it would be
nice, but I can understand not releasing the code, since it uses
private and undocumented routines (SPIs) which are bound to change
from version to version if not go away completely, and if the sources
were available, people would use these calls which would cause
serious compatibility problems as future versions of the OS are
released. There is probably also IP in there that they don't want
exposed...
Glenn Andreas email@hidden
<http://www.gandreas.com/> wicked fun!
quadrium | build, mutate, evolve | images, textures, backgrounds, art
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden