> I think the API could be simplified by having just one -sites accessor
> instead of two, allowing an optional "subscription" key that can be
> used to filter the items. This may also allow easier extensions in the
> future if we'd like that.

Sounds like a good idea to me. I'll implement that soon.

> I think hcite links can appear on various sites, it's a proposal for a
> generic microformat. Perhaps it could point to a general info page.

I see. I'll try to come up with a reasonable way to present this.

I wonder whether there is a magic BibTeX regexp  which could be used  
to recognise BibTeX in any web page. That'd certainly be useful.

> That should be easy when you can get the proper ID from the web page.
> In particular, it can just use +[BibItem(PubMedLookup)
> itemWithPubMedSearchTerm:], and use the current behavior when that
> fails.


Thanks for the pointer. I'll try to figure that out.

                Sven

-- 
Sven-S. Porst . http://earthlingsoft.net/ssp . AIM: cv47al
Pass as best inventor!


------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Bibdesk-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-develop

Reply via email to