> On Jan 16, 2019, at 10:43 AM, Jens Alfke <j...@mooseyard.com> wrote: > >> On Jan 16, 2019, at 8:32 AM, Carl Hoefs <newsli...@autonomy.caltech.edu >> <mailto:newsli...@autonomy.caltech.edu>> wrote: >> >> It was the NSData tie-in I didn't know. (I was expecting NSImage to have >> innate export capabilities > > That would be poor API design. If it had -writeToFile, then it would also > need -writeToStream:, -writeToFileHandle:, -writeToFileDescriptor:, > -writeToNSURLSessionDataDelegate:, etc. > Providing the data itself means you can then use existing APIs on other > classes to put the data anywhere you want.
But all of that would come "for free" if NSImage inherited from NSData, no? -Carl _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
