On Fri, 12 Oct 2001, Alexandros Vellis wrote:
> Is anyone anywhere considering making a jpilot "plugin" (conduit) for plucker?
> In essence, it will be a GUI front-end for Plucker.
As a tangental answer, I use Jpilot, and came up with a rather crude,
hackish manner of integrating their actions... I run the following script
via CRON:
------------------------------------Cut here---------------
export PATH=$PATH:/usr/local/bin/
if grep "today.pdb" /home/mattatkins/.jpilot/jpilot_to_install ;
then
echo "Missed yesterday!" ;
else
echo /home/mattatkins/.plucker/today.pdb >>
/home/mattatkins/.jpilot/jpilot_to_install;
fi
/usr/local/bin/plucker-build -f today
------------------------------------Cut here---------------
"~/.jpilot/jpilot_to_install" is where Jpilot queues it's to-be-installed
files, one per line, with carrage returns.
I realize this is more-than-marginally brute force, but it works for me.
If you want to be able to just point at something, pluck it, and have it
set up to be installed on next sync, this solution along with a little
creative scripting might help. For example, you could just set up a
script that plucks a subdirectory of your bookmarks, sets the given .pdb
up to be installed, then wipes the subdirectory of your bookmarks
clean - It'd probably also be a lot less work.
