[kepler-users] saving workflow in eps format

Edward A. Lee eal at eecs.berkeley.edu
Mon Mar 1 17:47:33 PST 2010


Yes, Christopher and I trying to figure out a way to make it easy
to import GPL'd plug-ins...  We tread a fine legal line however,
and could end up inadvertently GPLing (is that a verb?) all our
code...

Edward


On 3/1/10 5:41 PM, Peter Reutemann wrote:
>> The bottom line in this case is that we can provide instructions
>> for how to modify our source code so that you can export to PDF,
>> but we can't actually provide the code that does that...
>
> I'm not familiar with the Kepler code basis... But how easy would it
> be to provide a plug-in mechanism for "print" modules. Users would be
> able then to download these modules separately and enable print
> support, without having to modify the code basis (merely placing a jar
> in a "lib" directory and maybe making a small change to a props file).
> It should be possible to provide a Java-based installer for this kind
> of plug-in installation, I'd say.
>
>> Unless of course we write our own PDF utility and put it under BSD.
>
> A lot of effort, unfortunately.
>
> Cheers, Peter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: eal.vcf
Type: text/x-vcard
Size: 351 bytes
Desc: not available
URL: <http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/attachments/20100301/ee7d3af3/attachment.vcf>


More information about the Kepler-users mailing list