Re: Property List Editor displays number differently
Re: Property List Editor displays number differently
- Subject: Re: Property List Editor displays number differently
- From: Graham Jones <email@hidden>
- Date: Thu, 09 Jun 2005 10:37:29 -0400
Hi Hamish (& Andreas & Dave),
I must be not as good at searching as I thought I was... I'd love to use
Apple's plist APIs and far prefer that over osaxen, but I couldn't find
anything on Apple's side that could help me decode Base64 from am AS Studio
app.
I love math, but I am not excited about writing my own decoder either. And
I don't know enough Objective-C to strong-arm the routines I've seen into my
app.
Can you (or anyone) please help me fill in the blanks on how I can access
the appropriate API from an AS app (from within a script)?
It would seem that what I need to do is very simple... It's Apple's default
encoding for any <data> values in a plist file. It just seems so odd that
there's not an easy method to do this. All I need to do is take one number
from a <data> value and turn it into an integer (actually a numeric string).
Thanks,
Graham Jones.
On 6/8/05 3:32 PM, "has" wrote:
> Graham Jones wrote:
>
>> Hopefully there is a quick answer to this one
>
> Yep: use OS X's existing plist APIs. It'd be far quicker, simpler and more
> reliable to lever those via 'call method' or Satimage's XMLLib.osax. Trying to
> reinvent that wheel yourself will just create a lot of unnecessary work and
> problems. The whole reason Apple wrote that code in the first place was so
> nobody else would ever have to. :)
>
> has
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden