Re: [JPP-Devel] Porting Recent BizzJUMP Plug-Ins To OpenJUMP

[Michaël M. <mic...@fr...>]

Hi,

> After some discussions with Larry, Martin and others, I've decided to
> kill BizzJUMP, my independent fork of OpenJUMP, at least for the
> moment. This will allow me to contribute more of my efforts to
> OpenJUMP, and will help me avoid contributing to the name or brand
> dilution problem JUMP has.
>
> The first step in BizzJUMP's death will be the migration of BizzJUMP
> plug-ins to OpenJUMP. I've got to make some code changes to the
> plug-ins, because I was working with a modified plug-in management
> system. One of the other migration issues is the location of the menu
> items for the plug-ins in the OpenJUMP menu system. Here is where my
> plug-ins currently install:
>
> Super Select Tool Plug-In: Edit > Select > Super Select Tool
>
> Select Modified Features Plug-In: Edit > Select > Select Modified
> Visible Features
>
> Attribute Adder Plug-In: Attributes > Utilities > Add Attributes From CSV
>
> Find and Replace Layer Name Plug-In: Tools > Layers > Find and Replace
> In Layer Names
>
> Count Features Plug-In: Tools > Layers > County Features In Layer
>
> GPX Import Plug-In: Tools > GPS > Import GPX File
>
> Survey Point Import Plug-In: Tools > Survey Points > Import PNEZD Point File
>
> I think I need to make some changes to these menu locations in order
> to play well with OpenJUMP. Here is my first question:
>
> Should I integrate the GPX and Survey Point import plug-ins into the
> "Open File" system? My Survey Point plug-in looks for files with the
> CSV extension. Might this cause conflicts with some other plug-ins?
>   
Would be nice to use the Open File System. I must say I had hard time to 
understand Paul's framework for my csv plugin, but the framework manage 
both different formats with same extensions, formats with different 
extensions, and formats needing additional parameters.
If you want an example of how to incorporate an external plugin in the 
framework, have a look at 
http://geo.michaelm.free.fr/OpenJUMP/resources/drivers/txt-driver-src-0.2.zip 
<http://geo.michaelm.free.fr/OpenJUMP/resources/drivers/txt-driver-src-0.2.zip>
> Should all of the other plug-ins move under the top-level tools menu?
> Should I add a single "SurveyOS" entry under the tools menu where I
> group all of my plug-ins? Or should they be organized by functionality
> under the tools menu instead?
>
> I should note I won't be including these plug-ins in the core. They
> will be distributed separately, but I want to coordinate their
> integration into the GUI with the other OpenJUMP programmers.
>   
I would say that new tools should come in the Tools menu if they are 
distributed with the core, and should come in a new PlugIn menu for 
plugins which will stay external and optional.
Maybe a new PlugIns Menu should be included into MenuNames to avoid the 
multiplication of new main menus
What do you think ?
> Thanks for the help.
>
> Landon
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Jump-pilot-devel mailing list
> Jum...@li...
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
>
>