Thanks for the information Martin. The section of the JUMP Developer
Manual on Extensions was put together very well. After I read through
that section and took a peek at the Javadoc it made sense.
The Sunburned Surveyor
On 8/9/07, Martin Davis <[EMAIL PROTECTED]> wrote:
> You got it bang on, SS.
You got it bang on, SS. Extensions are intended as an easy way to add
arbitrary functionality to JUMP, with full programmatic control of the
configuration.
Note that as well as plugin classes, extensions may also add items to
the Registry, and new I/O drivers.
Sunburned Surveyor wrote:
> I'm
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Paul Austin
> Sent: August 2, 2007 1:25 PM
> To: List for discussion of JPP development and use.
> Subject: Re: [JPP-Devel] Understanding the purpose of the Extension
> class
PROTECTED] On Behalf Of
Paul Austin
Sent: August 2, 2007 1:25 PM
To: List for discussion of JPP development and use.
Subject: Re: [JPP-Devel] Understanding the purpose of the Extension
class in OpenJUMP.
Landon,
You are correct the purpose of the Extension classes are to install a
number of plug-ins
Landon,
You are correct the purpose of the Extension classes are to install a
number of plug-ins into the workbench.
Paul
Sunburned Surveyor wrote:
> I'm trying to figure out the best way to package the "built-in" or
> "default" pluggable renderers into OpenJUMP using my pluggable
> rendering s
I'm trying to figure out the best way to package the "built-in" or
"default" pluggable renderers into OpenJUMP using my pluggable
rendering system. I think I can do this with an Extension, but I want
to make sure that I understand the purpose of an Extension first, so I
don't use it improperly.
Th
