Hi Sean,
> On Jun 18, 2014, at 9:42 AM, Sean McBride wrote:
>
> On Tue, 17 Jun 2014 08:22:40 -0700, Tony Parker said:
>
>> NSKeyedArchiver and NSKeyedUnarchiver also support secure coding as of 10.9.
>
> Tony,
>
> Thanks for the details. Are there any issues in creating an archive on 10.9
>
On Tue, 17 Jun 2014 08:22:40 -0700, Tony Parker said:
>NSKeyedArchiver and NSKeyedUnarchiver also support secure coding as of 10.9.
Tony,
Thanks for the details. Are there any issues in creating an archive on 10.9
and then decoding it on 10.8 or older?
Cheers,
--
___
> On Jun 17, 2014, at 8:00 AM, Mike Abdullah wrote:
>
>
> On 17 Jun 2014, at 15:50, Sean McBride wrote:
>
>> On Tue, 17 Jun 2014 09:17:46 +0100, Mike Abdullah said:
>>
>>> I suspect the rationale might be “NSColor and NSImage live in AppKit,
>>> not Foundation, and the AppKit engineers aren’t
On 17 Jun 2014, at 15:50, Sean McBride wrote:
> On Tue, 17 Jun 2014 09:17:46 +0100, Mike Abdullah said:
>
>> I suspect the rationale might be “NSColor and NSImage live in AppKit,
>> not Foundation, and the AppKit engineers aren’t so bothered about secure
>> coding"
>
> That's a good theory. S
On Tue, 17 Jun 2014 09:17:46 +0100, Mike Abdullah said:
>I suspect the rationale might be “NSColor and NSImage live in AppKit,
>not Foundation, and the AppKit engineers aren’t so bothered about secure
>coding"
That's a good theory. So I just looked through Foundation and found numerous
other cl
On 17 Jun 2014, at 9:33 am, Sean McBride wrote:
> NSImage support only NSCoding
You don't want to be archiving NSImage objects if you can help it, FWIW. Some
variants don't even support it, like the one you get from the IKPictureTaker.
--Graham
On 17 Jun 2014, at 11:36, Maxthon Chan wrote:
> Personal suggestion, convert colors to strings (you can use any format, but I
> prefer #RRGGBB., drop the . for opaque color, which is compact and
> easily understood by humans) and images to PNG data (lossless), then archive.
Probably be
Personal suggestion, convert colors to strings (you can use any format, but I
prefer #RRGGBB., drop the . for opaque color, which is compact and
easily understood by humans) and images to PNG data (lossless), then archive.
On Jun 17, 2014, at 17:30, Greg Weston wrote:
> Sean McBride wo
Sean McBride wonders:
> I was modernizing some of my code to support NSSecureCoding instead of just
> NSCoding and stumbled upon that fact that NSColor and NSImage support only
> NSCoding and not NSSecureCoding. Whereas NSURL, NSData, NSArray and
> countless others now support NSSecureCoding.
On 17 Jun 2014, at 01:33, Sean McBride wrote:
> Hi all,
>
> I was modernizing some of my code to support NSSecureCoding instead of just
> NSCoding and stumbled upon that fact that NSColor and NSImage support only
> NSCoding and not NSSecureCoding. Whereas NSURL, NSData, NSArray and
> countl
On 17 Jun 2014, at 00:33, Sean McBride wrote:
> Hi all,
>
> I was modernizing some of my code to support NSSecureCoding instead of just
> NSCoding and stumbled upon that fact that NSColor and NSImage support only
> NSCoding and not NSSecureCoding. Whereas NSURL, NSData, NSArray and
> countl
Hi all,
I was modernizing some of my code to support NSSecureCoding instead of just
NSCoding and stumbled upon that fact that NSColor and NSImage support only
NSCoding and not NSSecureCoding. Whereas NSURL, NSData, NSArray and countless
others now support NSSecureCoding.
Is it just that Apple
12 matches
Mail list logo
