Hi Michael,
thanks for the changes. Meanwhile I went on exploring the menu structure of OJ
and I discovered that it is really easy to change menus and toolbars: that's
probabily one reason why Jump's tree became easly large. The temptation to
customize Openjump according to personal needs is quite strong, even for people
like me who have no experience on Java programming.
Just some preliminary observations:
1) Toolbar can be easly customized "via" JumpConfiguration. For instance,
using the class IconLoader it is possible to add whatever icons to the tools on
the Toolbar (es Iconloader.class "XXXX.png")
2) Moving plugin setup "back to JumpConfiguration" from defaul-plugins.xml it
is possible to reorganize and group plugins (es I added querry on datastore,
add datastore, refresh layer and change SRID to a unique menu/submenu
stucture)
3) actually JumpConfiguration file defines two layer tree menus (layers and
WMS). I image that it would be possible to add some more, like Datastore menu
that can be used to add specific tools, like Change SRID or refresh datastore.
4) It is possible to add some tools to the bar of the table, I checked that
Stefan did some tests on it.
These are the minimal observations. I can resume my impression on Jump
configuration to a typical american (and now international) expression: "Wow!" .
I will probabily make avaiulable a "personal OJ" in the next week (don't warry:
no official program to make another OJ clone).
regards
Peppe
--- Sab 5/3/11, Michaël Michaud <michael.mich...@free.fr> ha scritto:
Da: Michaël Michaud <michael.mich...@free.fr>
Oggetto: Re: [JPP-Devel] about layer tree - 1st test (and proposal)
A: "OpenJump develop and use" <jump-pilot-devel@lists.sourceforge.net>
Data: Sabato 5 marzo 2011, 14:01
Hi Peppe,
I have committed the change.
I did not use the file of your last mail for the following reasons :
- includes line numbering, which is not a big problem, but makes me wonder
where it comes from
- is quite different from svn version
- did not include line 1271 to 1275
Instead, I only changed SaveDatasetsPlugIn which now auto-install the plugin in
the ToolBar
I added an EnableCheck to the plugin constructor which makes the plugin
unavailable until there is a selected, writable, modified layer.
There are two new keys to be translated.
Modified source file and diff are available here :
http://jump-pilot.svn.sourceforge.net/viewvc/jump-pilot/core/trunk/src/org/openjump/core/ui/plugin/mousemenu/SaveDatasetsPlugIn.java?view=log
Modification will be available in next NB
Michaël
Le 22/02/2011 11:09, Giuseppe Aruta a écrit :
Hi all,
I did some tests on modifing JUMPConfiguration.class to change some menu
structure.
In this case I added SaveDatasetsPlugIn to toolbar, after NewTaskPlugIn.
The scope:
It seems to me the faster way to save a file while editing (one-click to save).
Just have a look to the screenshot I added to this mail.
My proposal, if other developers agree, is to add this modification to the
Openjump Toolbar (and I need somebody who can do this).
I added also the code of modified JUMPConfiguration,class. This code derives
from from OJ 1.4.0.3 source code and not from Night Snapshot.
The new lines I added are from 1271 to 1275
Regards
Peppe
--- Sab 19/2/11, Sunburned Surveyor <sunburned.surve...@gmail.com> ha scritto:
Da: Sunburned Surveyor <sunburned.surve...@gmail.com>
Oggetto: Re: [JPP-Devel] about layer tree
A: "OpenJump develop and use" <jump-pilot-devel@lists.sourceforge.net>
Data: Sabato 19 febbraio 2011, 20:35
Peppe,
I was home sick from work yesterday and I did some research
so I could
try to answer your question. Here is my attempt:
There are three (3) pop-up menus associated with the
LayerNamePanel in
each TaskFrame. One is for regular layers, one is for WMS
layers, and
one is for Categories. The TaskFrame.createLayerNamePanel
method uses
a nodeclassToLayerNamePopupMenu Map to determine which
pop-up menu to
associate with each type of "node" or item showed in the
LayerNamePanel.
This map is created in the WorkbenchFrame class. It
contains a member
variable called layerNamePopupMenu that is an instance of
the
TitledPopupMenu class. (The WMS Layer and Category pop-up
menus are
also instances of this same class.)
The FeatureInstaller class, which is used to install
plug-ins in
OpenJUMP, contains a method named addPopupMenuItem. This
method is
typically called in the initialize method of plug-ins that
want to add
menu item entries to one of the pop-up menus. You can take
a look at
the SelectAllLayerItems plug-in for an example of this.
To summarize this from a non-coder perspective, each
plug-in
contributes its own entry to the pop-up menus in the Layer
Tree. The
order of the menu items in the pop-up menu depends on the
order in
which plug-ins are initialized. To my knowledge, the only
way to
change the order in the menu is to create an Extension
(which extends
FeatureInstaller) that installs all of the plug-ins for the
pop-up
menus in the desired order, instead of allowing the
plug-ins to be
installed in some random order of initialization.
If all of the menu items in the pop-up menus are installed
by plug-ins
controlled in the JUMPConfiguration class, tweaking the
order of
plug-in installation there might work as well.
The Sunburned Surveyor
On Mon, Feb 14, 2011 at 9:40 AM, Giuseppe Aruta <giuseppe_ar...@yahoo.it>
wrote:
Hi all,
which class defines tool positions on layer tree?
thanks
Peppe
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R)
Parallel Studio XE:
Pinpoint memory and threading errors before they
happen.
Find and fix more than 250 security defects in the
development cycle.
Locate bottlenecks in serial and parallel code that
limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R)
Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the
development cycle.
Locate bottlenecks in serial and parallel code that limit
performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
------------------------------------------------------------------------------
Index, Search & Analyze Logs and other IT data in Real-Time with Splunk
Collect, index and harness all the fast moving IT data generated by your
applications, servers and devices whether physical, virtual or in the cloud.
Deliver compliance at lower cost and gain new business insights.
Free Software Download: http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
-----Segue allegato-----
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
-----Segue allegato-----
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel