On 11 Feb 2008, at 6:43 PM, Adam R. Maxwell wrote: > In article <[EMAIL PROTECTED]>, > Christiaan Hofman <[EMAIL PROTECTED]> wrote: > >> Adam, what about adding your RSS script to the bundle (in >> SharedSupport), > > Fine with me. Those were strictly for demo purposes to encourage > users > to write scripts; the compendex one is pretty useless. > > Note: SharedSupport is the wrong place for binaries (as is Resources), > according to recent posting on xcode-users. They should go in > Contents/MacOS for code signing, and for access with -[NSBundle > pathForAuxiliaryExecutable:. >
I'm not sure if I agree. SharedSupport is meant for extra support (re)sources that are not needed for the app to run (the built-in version of Application Support). MacOS seems to me more to be meant for executables used by the app. >> so it's easier to use. We could perhaps combine the >> compendix/pubmed scripts by adding an optional argument like "- >> pubmed" or something (we could add others ifthe need arises). The >> compendix script seems pretty generic to me, AFAICS it doesn't >> contain anything specific to compendix, correct? > > At some point I'd like to add better compendex support, but presently > it's generic RSS (IIRC...I haven't looked at it for months). > Personally, I'd prefer not to lump them into a single program; I like > the UNIX approach of small programs that are limited in scope. Sure, but for users who don't have programming skills it may be easy to have some easy to use executables to use for this purpose. That was my idea. It could also be a couple of scripts for common RSS posts. Christiaan ------------------------------------------------------------------------- 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
