Yes, installing GUI components is the primary use for extensions ... but
this is not there sole purpose.

Extensions are intended as a method of automatically injecting an
initialization routine into Jump. For example: reading properties,
loading layers, creating GUI components, checking for external drivers
... Installing plugins. 

Keep in mind, you will be executing in the GUI thread, so longer
exercises (for example creating DB connections) should be spawned in a
new thread.


  David Zwiers
  Vivid Solutions Inc. 

-----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 in OpenJUMP.

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 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.
>
> The JUMP Developer Guide says that: "An extension is a collection of 
> classes and supporting resources that provides additional 
> functionality to JUMP...The JUMP Workbench will search the JAR file
for 
> subclasses of Extension. (Note: They must also be named
"...Extension").
> It will then call the #configure method on each Extension class if 
> finds."
>
> It also contains this example:
>
> package example;
>
> import com.vividsolutions.jump.workbench.plugin.Extension;
> import com.vividsolutions.jump.workbench.plugin.PlugInContext;
>
> public class MyExtension extends Extension{
>
>   public void configure(PlugInContext context) throws Exception{
>     new HelloWorldPlugIn().initialize(context);
>   }
> }
>
> It seems to me the purpose of the Extension Class is to provide a 
> container that allows for the easy installation and configuration of a

> set of plug-ins and cursor tools. Is this correct?
>
> If this is the case I think I can use an Extension to configure and 
> install my "built-in" pluggable renderers as a group.
>
> Thanks,
>
> The Sunburned Surveyor
>
> ----------------------------------------------------------------------
> --- This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a
browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/ 
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>   



------------------------------------------------------------------------
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to