On 02/19/10 11:56, "Wesley Fraser" <[email protected]> wrote:
> I can handle entry creation and all that. The only catch is in the Bdsk-File-N > entry. I have seen a bunch of stuff about the net stating this is a base64 > encoded apple-uid containing string. I understand that. What I can't figure > out from looking through the bibdesk-trunk is just what methods are used to > encode/decode that string. > > So can someone either: > > 1) point out to me what methods are used to encode/decode that string, and in > what source files they are contained? Take a look at BDSKLinkedFile.m. Encoding/decoding is fairly straightforward, I think. > 2) With cocoa, explain how one would encode/decode that string? You can decode it from Base64 to a property list, but that's obviously an implementation detail. There's currently an alias data blob and a relative path; I don't remember if the new URL bookmark stuff in 10.6 provides a way to decode the alias data. There's a trivial PyObjC script here for dumping the plist contents: http://homepage.mac.com/amaxwell/.cv/amaxwell/Sites/.Public/read_bdsk_file.p y-zip.zip
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
_______________________________________________ Bibdesk-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
