1. Is there any way of adding private plugins that can be distributed
separately and don't have to be merged into the PPI executable?
2. Is the interface sufficient to allow for different kinds of
data/commands to be passed, beyond a simple lookup?
A possible #3, based on #1
From: David A. Desrosiers [EMAIL PROTECTED]
My concern here is that contributors/companies circumvent the
functions provided by Plucker, or add additional useful features, by
writing their own non-Free plugins.
On the other hand, it'd be handy to be able to write one's own plugins for
private
---Reply to mail from David A. Desrosiers about Plucker Plugin Interface
Robert first:
If you'd like to try it, untar the attached (ppi.tgz) in the viewer
directory. You should be able to just install ppi_en.prc and then load a
modified viewer_XX.prc. The only modification is to change
---Reply to mail from Alexander R. Pruss about Plucker Plugin Interface
On the other hand, it'd be handy to be able to write one's own plugins for
private use and not have to have them be patches against the PPI code. (For
instance, I'd like to have a plugin that strips accents from an input
On Mon, Dec 29, 2003, Michael Nordstrom wrote:
At the moment you have to apply the attached patch to the PalmCUnit
code, but I will contact the current maintainer of PalmCUnit and
check if he could make these minor changes to the main source code.
The changes have been included in the main
Looks nice (apart from the help texts that are taken from the cleaner!) I
think ideally it should have an editable database of programs that it can
launch, preloaded with the items already there.
One way to do this is have a drop-down list of program entries, with four
buttons under it:
select
I suppose one plausible closed-source use someone might make of PPI is that
once record-loading is included in PPI, a closed-source developer might make
a DRM module for Plucker. Whether this is a bad thing depends what one
thinks of DRM. (Current Plucker DRM is, I take it, not very good, since
