Re: Scheme for efficiently archiving images.
Re: Scheme for efficiently archiving images.
- Subject: Re: Scheme for efficiently archiving images.
- From: Jens Miltner <email@hidden>
- Date: Thu, 27 Nov 2008 14:30:18 +0100
Am 27.11.2008 um 07:54 schrieb Graham Cox:
On 27 Nov 2008, at 2:00 pm, Ken Thomases wrote:
First, it seems to me like you don't want an NSImage in your
model. You want the original source of the image. Either a file
path or a blob of data with some meta-data (e.g. UTI) describing it
and what it is. You'd use NSImage as a view-enabling technology.
Yep, this is precisely how I'm coming to see it. One kink is that I
need to keep old-format stuff working, which isn't too hard, but it
means I need to be a little careful about how I eliminate NSImage
from the archived model. One minor difficulty is that for old-format
files, all I get is an archived NSImage, with no original data. That
means that it's probably going to be impossible to convert those
files to a more efficient approach.
Well, you _can_ ask the NSImage or it's rep for a certain bitmap
representation (see e.g. <http://markmail.org/message/
urbmcjwh5vixoxfd>).
Even if the NSImage can't provide that data, you could still use the
BSD layer to convert to e.g. a JPEG: man sips
HTH,
</jum>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden