On 29 Jan 2009, at 7:56 PM, Maxwell, Adam R wrote: > On 01/29/09 09:21, "Christiaan Hofman" <cmhof...@gmail.com> wrote: > >> Anyway, the check as it is currently shouldn't be necessary. > > Only for autocomplete, as I was surprised to find.
Also when it's not appearing in the Editor? > I had to add that case > in the parser because I'm using openssl for base64 instead of Omni's > decoder, and it seems to be stricter about line breaks and spaces. Good to know, as I've also added that to Skim. Though not in any way where this could be a problem. > Which > wasn't a problem until I sent a message to myself from work using > Entourage. > I don't recall why I used openssl in the first place...a quick > glance at OF > tells me that I was probably trying to avoid temporary objects. > > Actually, I think it would be cool to eliminate the Omni frameworks > entirely, although the preferences window alone makes that a really > daunting > task. Yea, there's a lot of stuff in it I really don't like. Such as implementation overriding Leopard API and far too many swizzling. But indeed it would be a lot of work to change everything. As for the pref window, I believe there's also alternative implementation for that alone (though I don't know how good they are). Talking about that, when I was looking into the runtime implementation to improve method swizzling in Skim I was really surprised that the old runtime system wasn't thread safe! Only in 10.5 did they add locks, but not everywhere. And Omni's implementations were originally using the thread-unsafe stuff even on Leopard (that's changed now). Christiaan ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Bibdesk-develop mailing list Bibdesk-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
