there has been an extension manager, but this one was rather for 
downloading available plugins. the code is still there, but could be 
that the plugin needs to be activated (in the xml file)

stefan

Michael Michaud schrieb:
> Hi,
> 
> There used to be a plugin manager in the menu, but I cannot find it anymore.
> It was from lat/lon if I remember correctly, but I'm not sure it has 
> ever been used the project's plugin.
> Anyone remember ?
> 
> Michaël
> 
> Sunburned Surveyor a écrit :
>> I've got about four plug-ins that I hope to release in January. This
>> includes my reader for GPX files, the latest edition of the Super
>> Select Tool, and a couple of Layer Utilities plug-ins.
>>
>> Some of these are simple plug-ins with a single Jar and no
>> dependencies. So you can just drop them into the /ext folder of
>> OpenJUMP. Other of my plug-ins, like the Super Select Tool and the GPX
>> Reader, depend on external libraries and have I18N and configuration
>> files. I had cooked up part of an installer for the Super Select Tool
>> when I got to thinking that it might be nice to have a tool that could
>> be used to install, uninstall, and update plug-ins for OJ. It wouldn't
>> have to be a part of OJ, it could even run as a separate executable.
>>
>> I was thinking of this simple interface:
>>
>> public interface PlugInHandler
>> {
>>    public abstract void installPlugIn(File argOpenJumpFolder);
>>      
>>    public abstract void uninstallPlugIn(boolean argRemoveSharedLibraries);
>>      
>>    public abstract void updatePlugIn();
>> }
>>
>> I was thinking of another interface that could be used by
>> PlugInHandler.installPlugIn method implementations to show a standard
>> GUI to the user during plug-in installation/update:
>>
>> public class PlugInInstallerGuiProvider
>> {
>>      public abstract JPanel getLicensePanel();
>>      
>>      public abstract JPanel getInstallConfigurationPanel();
>>      
>>      public abstract JPanel getAboutPanel();
>> }
>>
>> I thought a library providing these interfaces and some default
>> implementations might help us standardize plug-in management and make
>> the process of installing and removing plug-ins a little easier on the
>> end user.
>>
>> Do you guys have any comments on this?
>>
>> The Sunburned Surveyor
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>> Build the coolest Linux based applications with Moblin SDK & win great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> 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 the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> 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 the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to