On Wednesday, October 03, 2007, at 08:59AM, "Michael McCracken" <[EMAIL 
PROTECTED]> wrote:
>On 10/3/07, Simon Spiegel <[EMAIL PROTECTED]> wrote:

>> > I sort of like this idea, and I believe that it will be getting easier
>> > to write such plugins for safari in 10.5.
>> >
>> > I only say 'sort of' because I don't use safari all the time, I
>> > believe Adam is an OmniWeb user, and I think this is representative -
>> > we would have to write plugins for many browsers.

Yup, I've been an OW user ever since OS X Public Beta, except for a brief 
period of using Chimera.

>> Not that I know anything about the technical details, but OmniWeb is
>> based on WebKit. Wouldn't a WebKit-based plugin be possible? This
>> would cover many browsers, and Gecko-based browsers are already
>> covered with Zotero.
>
>My last understanding was that they used the lower levels of web kit
>for rendering but didn't use all of it. I'm really not sure, but at
>any rate it's easier to build it into BibDesk, and let BD read the
>browser's bookmarks for integration.
>Maybe the upcoming changes to webkit will change that.

Omni switched to using WebKit instead of their own customized WebCore a while 
ago, so we lost things like ATS font rendering, but gained some compatibility 
and performance.  I wrote a WebKit plugin that recognized the RIS MIME type and 
automatically loaded it into BibDesk, but I was never happy with it; for one 
thing, it requires a MIME type to be useful.  Improving the experience in 
BibDesk would be easier and more profitable for us, in my opinion.

adam

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bibdesk-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-develop

Reply via email to