Hey,

I would be a huge fan (since I would write a plugin which works better  
with NASA ADS than the current Z39.50 support (through no fault of  
BibDesk).

I kind of suggested this via the following plan: make script groups  
accept arguments, which can be provided through the UI in a Search  
Group type fashion. This *seems* like it would be pretty straight  
forward, and capitalise on existing code.

I haven't had time to follow up the suggestion. (Code base sitting  
unopened on my laptop, if only there were more hours in a day!)

Cheers,
Andy


On 17/02/2008, at 2:10 PM, Michael McCracken wrote:

> Hey, I just saw this. A plugin api seems like a decent idea for web
> scrapers, and I believe it'd be easy enough to support ruby and python
> via the pyobjc/rubycocoa bridges - at least in the python bridge,
> there are no problems defining a pyobjc subclass of an ObjC class...
>
> If possible, it'd be a very good idea to incorporate Alf Eaton's work
> on javascript, since it seems like there's lots of work in Zotero's
> scrapers we could be using. I just wish I had time to work on using
> external javascript in web views. There's a coding headstart about it
> on apple's developer site that I've had on my 'to-read' list for a
> long time...
>
> I think the pattern goes something like this - you get the script
> object from a webframe (or webview), and you can have it execute any
> code you want, and that code can access the page content, and could
> conceivably change properties in objc objects you let it know about.
>
> I never got a chance to look closely at Alf's work. His code is here:
> http://code.google.com/p/jqscrapers/
> and his post about it is here: http://hublog.hubmed.org/archives/001560.html
>
> -mike
>
> On Jan 19, 2008 11:29 AM, Adam R. Maxwell <[EMAIL PROTECTED]> wrote:
>> How hard would it be to have a plugin API for web groups?  The  
>> biggest
>> problem I see ATM is using an enum for types, since that can't be
>> supplemented at runtime.  The BDSKWebParser API is pretty simple,
>> otherwise.
>>
>> It would be further cool if they could be implemented in python/ruby/
>> perl since users are more likely to be able to use those; maybe we
>> could provide a generic Obj-C wrapper that launches a script.
>>
>> I know in the past we've decided not to implement a plugin API for
>> parsers, but it seems like plugins could be a bigger potential win  
>> for
>> the web group.  A more complicated approach would be allowing search
>> group plugins, but I think our threaded architecture would make that
>> too hard.
>>
>> Worth asking the users list to see if anyone would care?  Papers  
>> seems
>> to get a fair amount of mileage out of user-written plugins, and I
>> think the Books program uses python plugins.
>>
>> --
>> adam
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Bibdesk-develop mailing list
>> Bibdesk-develop@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
>>
>
>
>
> -- 
> Michael McCracken
> UCSD CSE PhD Candidate
> research: http://www.cse.ucsd.edu/~mmccrack/
> misc: http://michael-mccracken.net/wp/
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bibdesk-develop mailing list
> Bibdesk-develop@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bibdesk-develop


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bibdesk-develop mailing list
Bibdesk-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bibdesk-develop

Reply via email to