jpilot-plucker A J-Pilot plugin for Plucker. THIS IS _NOT_ A PLUCKER-DESKTOP PLUGIN. You must have the plucker distiller installed and valid .pluckerrc and home.html files for this plugin to be of any use. by Jason Day http://www.jlogday.com ----------------------------------------------------------------------- REQUIREMENTS - J-Pilot version 0.99.2 or greater, available from http://www.jpilot.org - Plucker (http://www.plkr.org) BUILDING First, determine where J-Pilot is installed. If you installed J-Pilot from an rpm or other binary package, it is probably in /usr/bin. Use your distribution's package management tools to find out for sure. Or try "which jpilot" from a command prompt. If you compiled J-Pilot yourself, you should know where you installed it. Next you need to find out if J-Pilot was built with GTK2. You can find this out by clicking J-Pilot's Help menu and choosing J-Pilot. Now you are ready to build jpilot-plucker. First, extract the jpilot-plucker tarball. Now change to the jpilot-plucker-x.xx directory and run configure, passing in the J-Pilot prefix and enabling GTK2 support if necessary. For example, if J-Pilot is installed in /usr and was built with GTK2, you would execute this command: ./configure --prefix=/usr --enable-gtk2 Type "./configure --help" for more options. Once the configure script has finished, build the plugin by typing "make". Assuming it builds without errors, you can install the plugin in one of two ways: For a system-wide install (available to all users), become root and type "make install". For a user installation (available only to you), just type "make local_install". USAGE After installing, (re)start J-Pilot, and choose Plucker from the Plugins menu. This will display the jpilot-plucker gui, which for now is just a preferences screen. From here, you can choose when to run the plucker distiller, the distiller command, whether to run the distiller in a terminal, the terminal command, and the directory to install plucker documents from. You can also run the distiller manually by clicking the "Run Distiller" button. The distiller command will be run inside of /bin/sh, so you can use shell variables and/or commands. e.g. "slashpluck.pl && plucker-build" -- this will first execute slashpluck.pl and, if it returns a 0 exit code, will then execute plucker-build. This is NOT the case for the terminal command; if you choose to execute the distiller in a terminal, you must use a single command without arguments or variables. e.g. "xterm" or "gnome-terminal". If you do not use a terminal, the output of the distiller process will be displayed in J-Pilot's output window. The "Install from" directory is the distiller's output directory. Any files with a .pdb extension in this directory will be installed to the palm. jpilot-plucker will NOT recursively descend into subdirectories. This directory must be a full path, with no shell variables. i.e. Use "/home/jday/.plucker", not "~/.plucker" or "$HOME/.plucker". BUGS - If you change anything on the gui, make sure you save the changes before you try to sync. You may get unexpected results if you do not. - If you use a terminal, the terminal will exit as soon as the distiller process is finished. Anybody know how to stop this? xterm has a -hold option, but rxvt and gnome-terminal do not. If you find a bug, please send a message to jason@jlogday.com . It would also be helpful to start J-Pilot in debug mode (jpilot -d), reproduce the bug, and send the contents of ~/.jpilot/jpilot.log in the message. Thank you for using jpilot-plucker! Jason Day