@Troy: Should I just drop NSImage all together and just focus on being good at the Core Image framework, and if so, then what's the point of NSImage
NSImage and CIImage don't do exactly the same things. There's some overlap, but deciding which one to use really depends on what you're doing.
It's hard to sum both up in a few sentences, but basically NSImage is a container for NSImageReps. The representations can be bitmaps or vectors, and the idea is that NSImage chooses the best one for the context. CIImage is more built around filters and transformations of bitmaps and makes use of the graphics card for faster performance in certain areas.
If it looks like Core Image will work better, go ahead and use it. If you're not doing a lot of filtering and transformations, though, there's probably not much to be gained by using switching.
If you can be more specific about what you're working on, I can give more specific suggestions.
by Scott Stevenson — Dec 17
NSImage and CIImage don't do exactly the same things. There's some overlap, but deciding which one to use really depends on what you're doing.
It's hard to sum both up in a few sentences, but basically NSImage is a container for NSImageReps. The representations can be bitmaps or vectors, and the idea is that NSImage chooses the best one for the context. CIImage is more built around filters and transformations of bitmaps and makes use of the graphics card for faster performance in certain areas.
If it looks like Core Image will work better, go ahead and use it. If you're not doing a lot of filtering and transformations, though, there's probably not much to be gained by using switching.
If you can be more specific about what you're working on, I can give more specific suggestions.