 |
 |
ADC and "Private" API
|
|
|
|
|
Fresh-Faced Recruit
Join Date: Feb 2001
Location: Seattle, USA
Status:
Offline
|
|
To the notice (and chagrin!) of many, significant parts of the API have been kept private in the Beta.
1. Will Apple release more API, or are we going to have to spend
the next few years reverse-engineering this puppy?
2. Does Apple release more API to for-pay members of its development
programs than to freeloaders like myself?
Your perspective is appreciated.
|
|
|
| |
|
|
|
|
|
|
|
Forum Regular
Join Date: Dec 2000
Status:
Offline
|
|
Obviously, I haven't been doing enough development. What parts of the API are private?
|
|
|
| |
|
|
|
|
|
|
|
Senior User
Join Date: Nov 2000
Status:
Offline
|
|
Ya'know those sleek transparent windows...private.
That's about all I know of. 
I'm sure they'll release what they think everyone should know about. APIs that aren't done or need to be used a special way might be kept private until they're done but other than to "protect" us I don't see why Apple would keep a bunch of stuff hidden.
I know I tend to whip up stuff that works but that I wouldn't want anyone else to use. I know how to use it and it works for what I need to do but I wouldn't waste my time documenting it and then toss it up in the air for a free-for-all. I'd probably think about the design, do a re-working of alot of stuff, test a bit, document and then toss it out into the open.
Supposedly all the neat widgets (sliding tabs and whatnot) they use will be available later. I don't really know enough about it but I'd imagine alot of the stuff that's private now will come out of the closet later.
______________________________________
2¢? I didn't even ask for a penny!
|
|
|
| |
|
|
|
|
|
|
|
Mac Enthusiast
Join Date: Feb 2000
Location: Storrs,Connecticut, USA
Status:
Offline
|
|
Maybe he means all of the stuff that is in the Private Frameworks folder?
|
|
|
| |
|
|
|
|
|
|
|
Senior User
Join Date: Nov 2000
Status:
Offline
|
|
And I was just saying that maybe the stuff in the Private Frameworks folder won't always be there.
That stuff could be there now because it's is in flux and not presentable (yet). Or, it could just be that Apple is being stingy and doesn't want anyone to use it.
I have no clue really. I was just making a guess.
|
|
|
| |
|
|
|
|
|
|
|
Forum Regular
Join Date: Dec 2000
Location: Rehoboth Beach,DE USA
Status:
Offline
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
Admin Emeritus  Join Date: Oct 2000
Location: Boston, MA
Status:
Offline
|
|
I'm not at my home computer, but transparent windows are accomplished by something like
extern int _NSSetWindowAlpha(int window, float value)
I'm guessing it just needs more fine-tuning, or that Apple has a few surprises that will replace setting window alpha like this.
|
|
"Against stupidity, the gods themselves contend in vain" (Schiller)
|
| |
|
|
|
|
|
|
|
Dedicated MacNNer
Join Date: Feb 2001
Status:
Offline
|
|
The easiest way to make a transparent window (in Cocoa) is to have your NSWindow subclass implement a _transparency method, like this:
-(float)_transparency {
return 0.8f; // 1 is fully opaque, 0 is invisible
}
To see how to write screensavers, go to www.epicware.com and download the OS X screensaver pack; many of them include source.
Of course since both of these are undocumented, they could easily change on 3/24...
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
|
Top
