Re: [Pyobjc-dev] In and out of NSData

[<bb...@ma...>]

On Tuesday, Jan 7, 2003, at 18:33 US/Eastern, Jack Jansen wrote:
> Carbon.CF is in there, albeit through an oversight of either myself or 
> Apple. The only problem is that it is called "_CF" only (that's the 
> internal name, the external name should be "Carbon.CF").

> But note that my note was more aimed towards development of PyObjC 
> itself: I think we should tie in more to what is already available 
> than try to do everything from scratch.

Why not just 'CoreFoundation'?   Part of the reason that I have been 
somewhat hesitant about dipping into the MacPython stuff is that it 
seems [may be my complete ignorance] to be oriented very much to Carbon 
-- the Core isn't directly accessible without dragging in Carbon?

I would liked to keep PyObjC in line with Apple's model for the system; 
   not what is there now, but the direction they have repeatedly 
emphasized at WWDC over the last N years.   That is, Cocoa is on top 
Core and Carbon is on top of Core, but Cocoa and Carbon are relatively 
separated.

A goal, anyway.

But, yes, overall, PyObjC should not re-invent wheels that already 
exist, work well, and have been tested by a large community.

b.bum