Wiz -- you'd have to make a sh-script, and associate it to the .pdf extension; the sh-script woudl then just be: pnd_run $0
I debated adding that in (as per the PXML spec), but at the time I had a bunch of unresolved concerns so decided to 'let it ride', and deal with it as the community encountered -- ie: I wanted to garner actual usage experience from people using the system before I went and complicated it all up. However that said, its a pretty easy addition to libpnd that I've thought about a couple of times, so I could add it in over a weekend
(ie: when pndnotifyd sees a note in PXML, then check the freedesktop set of xml files for the association, and if different, change it to the one in question; or create a .desktop file association, I think that works as well. I forget particulars now offhand, but not hard to do.)
(Same sort of thing for 'shared lib' type pnds; ie: for those, they need 1) an autorun directory, such as /pandora/autorun, and 2) afgter mounting, and exiting, they need a PXML flag that says 'do not unmount'; these points imply 1) security riskfor _autorun_, and 2) how do you unmount these long-mounting guys? Also worry over.. any time you do an eject/insert, with a long mounted lib, we guarantee a /media/mmcblk number change. An option is to copy the lib from the autorun to /tmp, so that the pnd can unmount immediately, and LD lok at /tmp/libs to get them; but then we have RAM overrun (or if using another directory, a NAN D overrun) problem... so you see, it became easy for me to think 'lets see how it goes.) Also not hard to add
So a couple key ideas are currently out.
But feel free to comment .. I could add them in easy, just wasn't sure what direction to go yet
jeff