On 9 Jun 2013, at 06:23, Jens Alfke <[email protected]> wrote:
>
> On Jun 8, 2013, at 12:24 PM, Ken Thomases <[email protected]> wrote:
>
>> I haven't done the experiment, but I don't believe this is necessarily true.
>> NSBitmapImageRep is documented (in the Snow Leopard release notes) as
>> keeping the original image data and not re-encoding or exploding file sizes
>> on being saved.
>
> I did not know this — guess I haven’t been reading the release notes closely
> enough.
url = some/picture.gif
NSDataReadingOptions mask = 0; // NSDataReadingUncached
NSData *data = [ NSData dataWithContentsOfURL: url options: mask error:
&outError ];
got 19420 bytes
NSImage *image = [ [ NSImage alloc ] initWithContentsOfURL: url ];
BOOL ok = [ NSArchiver archiveRootObject: image toFile: @"/tmp/anImage"
];
got 307559 bytes (NSKeyedArchiver adds another half kB)
This 16-fold increase of data is - regardless of image quality - not acceptable
for my purposes.
So I will use dataWithContentsOfURL (and switch to NSURLConnection once the
unresponsiveness of the app becomes annoying).
I still have no idea why my image delegate never gets messaged. But not
important anymore.
Kind regards,
Gerriet.
_______________________________________________
Cocoa-dev mailing list ([email protected])
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 [email protected]
