> Would that be packaged as a shared library or a separate application? If
> my application is commercial, I can't just include Plucker source code,
> can I?
You would be writing a reader, from scratch, that can read the
Plucker document format, based on the existing Plucker document API. If you
took this route, you wouldn't be able to use code that already exists in
Plucker to do it. You would have to create your reader from scratch, using
the public API.
If, however, you wanted to use Plucker's source code directly in the
reader, that component would have to be covered by the GPL, as a derivitive
work of Plucker itself. There is no reason why these can't be two separate
applications: 1.) Your commercial application (non-free), and 2.) a small
reader that can read Plucker documents (GPL). You can strip quite a lot of
functionality out of Plucker to make a "slim" reader if you wish, to make
this happen.
If you wish to make having Plucker onboard, a requirement for your
application, with the intent of sub-launching Plucker from within your
commecial application, you'll have to make modifications to Plucker directly
to support the "Exit" function, as we've been discussing.
Here's a thought... what about adding a function code, in the
document itself, that would force an exit of Plucker, when tapped?
d.
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
