Extend plugin architecture
Posted: Sun Feb 08, 2009 4:20 pm
I'm looking into Bookpedia. It's cool and potentially very powerful. But not really powerful because it lacks of a useful search function for me (Spain). Casadellibro is a nice physical library, but pure crap searching for ISBNs. This must be a common problem for many countries, I think. These folks only provide ISBN numbers for books they sell or they can acquire for you. But this is absurd and un-usable if I want catalog my own books. I guess you heard this or something similar before
Plug-ins are OK, if you speak Cocoa.
I speak a couple of programming languages and my favorite one for desktop programming is AppleScript.
Appart of a Xcode template, which is useful for obj-c programmers, why don't you provide a pre-compiled plugin with some instructions for other non-obj-c developers? Specifically, and for example, you can include a special folder from where obj-c tells the system to *run* whatever thing is in there called "plugin" (plus extension). For example, it would run "plugin.sh" or "plugin.pl" or "plugin.py" or... And it would be nice if it could run as well "plugin.scpt" (for AppleScript). But if it can run "plugin.sh" we can allways use "osascript" from inside the shell script... A very simple "sample.sh" would do the job, as a shell script can run most of these languages (python, applescript, ruby, perl...).
You will pass a parameter to this file, the ISBN and you will wait for the answer (a collection of key-values with info about the found results?).
I'm sure there are lots of issues and caveats with this suggestion, but this could easily open your plugin architecture to many or ALL programmers in the Mac OS platform... --> and would make Bookpedia a click'n'go app for me
Plug-ins are OK, if you speak Cocoa.
I speak a couple of programming languages and my favorite one for desktop programming is AppleScript.
Appart of a Xcode template, which is useful for obj-c programmers, why don't you provide a pre-compiled plugin with some instructions for other non-obj-c developers? Specifically, and for example, you can include a special folder from where obj-c tells the system to *run* whatever thing is in there called "plugin" (plus extension). For example, it would run "plugin.sh" or "plugin.pl" or "plugin.py" or... And it would be nice if it could run as well "plugin.scpt" (for AppleScript). But if it can run "plugin.sh" we can allways use "osascript" from inside the shell script... A very simple "sample.sh" would do the job, as a shell script can run most of these languages (python, applescript, ruby, perl...).
You will pass a parameter to this file, the ISBN and you will wait for the answer (a collection of key-values with info about the found results?).
I'm sure there are lots of issues and caveats with this suggestion, but this could easily open your plugin architecture to many or ALL programmers in the Mac OS platform... --> and would make Bookpedia a click'n'go app for me