ok, had a look into it. unfortunately not done easily , so forget about it ;)
better look up if you can find a proper JMultiLineToolTip implementation. make sure it is public domain or GPL2 before integrating into core. btw. i saw you added LayerNameRenderer.getExtension(File f) . unnecessary we already have such functionality in com.vividsolutions.jump.util.FileUtil ;) ..ede On 31.03.2015 22:40, Giuseppe Aruta wrote: > Hi Ede, > 2 times layer tree panel seems to me too short for path. Anyhow I will adopt > your suggestion and see how it works. My problem is that I don't know how to > get the width of Layer Tree Panel. Do we have a way to calculate it? > Peppe > > 2015-03-31 15:56 GMT+02:00 <edgar.sol...@web.de <mailto:edgar.sol...@web.de>>: > > two notes: > > 1. why add an extra panel to configuration? it would fit unter > 'View/Edit' i'd say. > 2. 400px still looks excessive. what about the 2times Layertreepanel > width i suggested? > > ..ede > > On 31.03.2015 15 <tel:31.03.2015%2015>:02, Giuseppe Aruta wrote: > > I fix the problem. It should be OK on next buld. > > > > When you launch fresh instalation of OpenJUMP, on Customize>Options > plugin, you will find another panel called "Configure tooltips". > > > > > > > > The panel has only one option enabled "Enable JUMP basic tooltips". > > Which is the basic tooltip of JUMP/OpenJUMP untill ver. 1.8 > > > > > > Deactivating the box on "Enable JUMP basic tooltips", moving cursor > over the layer will show the other type of tooltip with more info. Regarding > Layer. class, users can check between layer with datasource, layers with > datasources and changes to save, layers with no datasources. > > > > Example with a layer with datasources and changes to save > > > > > > Example of layer with no datasource > > > > > > > > The advanced tooltip has been fixed to a maximum of 400 px. So any > longer path will be broken in multiple lines > > See the example below > > > > > > I used a part of code from SAIG Kosmo project. > > There are some language code that aren't internationalize. I will do > this job on next weeks. > > Best regards > > Peppe > > > > 2015-03-31 11:24 GMT+02:00 Giuseppe Aruta <giuseppe_ar...@yahoo.it > <mailto:giuseppe_ar...@yahoo.it> <mailto:giuseppe_ar...@yahoo.it > <mailto:giuseppe_ar...@yahoo.it>>>: > > > > Hi Jukka, > > I am going to check in the afternoon > > Peppe > > > > 2015-03-31 8:46 GMT+02:00 Rahkonen Jukka (MML) > <jukka.rahko...@maanmittauslaitos.fi > <mailto:jukka.rahko...@maanmittauslaitos.fi> > <mailto:jukka.rahko...@maanmittauslaitos.fi > <mailto:jukka.rahko...@maanmittauslaitos.fi>>>: > > > > Hi,____ > > > > __ __ > > > > Snapshots do not build, see > http://sourceforge.net/projects/jump-pilot/files/OpenJUMP_snapshots/OpenJUMP-20150331-r4362.log/download____ > > > > __ __ > > > > -Jukka Rahkonen-____ > > > > __ __ > > > > Giuseppe Aruta wrote:____ > > > > __ __ > > > > Hi all,____ > > > > I made an upgrade to OpenJUMP NB, about tooltips____ > > > > - now tooltips are configurable via "Configure tooltips" option > on Configure panels____ > > > > - there are two options:____ > > > > a) original JUMP/OpenJUMP minimal tooltip, which displayes > only number of feature____ > > > > This option is set by default when launching OJ for > the 1st time____ > > > > b) advanced info tooltip The size is limited to 400px > width and long file paths are broken in several > > lines. IN this option I saved different colors (red > and blue) > > to display layer with no datasource and modified > layer with datasource in the tooltips____ > > > > The option choosen by user is saved into workbench-state.xml > file, so it will be recognized by OJ when it is launched the second time____ > > > > Please check next OJ build____ > > > > Giuseppe Aruta____ > > > > __ __ > > > > __ __ > > > > 2015-03-30 14:38 GMT+02:00 Giuseppe Aruta > <giuseppe_ar...@yahoo.it <mailto:giuseppe_ar...@yahoo.it> > <mailto:giuseppe_ar...@yahoo.it <mailto:giuseppe_ar...@yahoo.it>>>:____ > > > > Some datasource-less layers can be in the middle of an > analysis, and not having any value/interest to save into the project. > > For instance:"Layer A (datasource layer) generates Layer B( > datasource-less layer), which generates Layer C ( datasource-less layer), > which generates End Layer D"( datasource-less layer). > > Where probably only Layer A and D are of any interest in the > project.t____ > > > > I feel we should give the user to understand which /_layer_/ > has a datasource or not. But also which /_file _/should be committed or not > as its layer has been changed.____ > > > > Peppe____ > > > > __ __ > > > > __ __ > > > > 2015-03-30 11:07 GMT+02:00 <edgar.sol...@web.de > <mailto:edgar.sol...@web.de> <mailto:edgar.sol...@web.de > <mailto:edgar.sol...@web.de>>>:____ > > > > actually just one * should suffice for any modified (since > creation or last saved) layer. or is there any advantage for users to > identify datasource-less layers? > > > > ..ede > > > > On 30.03.2015 09:48, Giuseppe Aruta wrote: > > >> - layers without datasource ** (are probably created during > runtime, so > > > there is a >probability that the user wants to save those) > > >> - layers with datasource and unsaved change * > > >> - layers with datasource and no unsaved change (nothing, > cause all is well > > > wrt. >to these) > > > > > > Going back to this proposal, It looks good for me. > > > Peppe > > > > > > 2015-03-27 8:21 GMT+01:00 Giuseppe Aruta > <giuseppe_ar...@yahoo.it <mailto:giuseppe_ar...@yahoo.it> > <mailto:giuseppe_ar...@yahoo.it <mailto:giuseppe_ar...@yahoo.it>>>: > > > > > >> @ Ede, > > >> I also considered to break the lines: > > >> > > >> > > >> I dropped this ways as the problem of tooltip areal > dimension was not > > >> solved: long path will create huge tooltips. Which is > probably what > > >> confuses an user, especially people who have the attitude to > save lots of > > >> files in lots of folder/subfolders/(su-sub-folders). I > should consider > > >> more variabilities: length of tooltip, font dimentions, etc: > I will adopt > > >> Michael's idea ("simple is better") and use a tooltip as > simple as > > >> possible, but showing the most useful information (layer, > unsaved, > > >> modified, num of items). > > >> Anyhow I will save the old code (in LayerNameRenderer.class) > and will work > > >> around in the future. > > >> > > >> @Andrei > > >> the tooltip stays. I will study a way to make it > enable/disable > > >> > > >> I am waiting Jukka and Michael's (possibly others') > suggestions before > > >> applying any modification > > >> > > >> Peppe > > >> > > >> > > >> 2015-03-26 23:49 GMT+01:00 sstein <sst...@geo.uzh.ch > <mailto:sst...@geo.uzh.ch> <mailto:sst...@geo.uzh.ch > <mailto:sst...@geo.uzh.ch>>>: > > >> > > >>> looks good to me too :) > > >>> > > >>> > > >>> ------ Originalnachricht ------ > > >>> *Von: *Andrei Nacu > > >>> *Datum: *26.03.2015 13:14 > > >>> *An: *OpenJump develop and use; > > >>> *Betreff:*Re: [JPP-Devel] Tooltip again > > >>> > > >>> I like the proposed tooltips. They look better and less > intrusive now. > > >>> Will the new tooltip stay as it is now, or will it become > optional? > > >>> > > >>> Andrei > > >>> > > >>> > > >>> > > >>> On Thursday, March 26, 2015 6:35 PM, Giuseppe Aruta < > > >>> giuseppe_ar...@yahoo.it <mailto:giuseppe_ar...@yahoo.it> > <mailto:giuseppe_ar...@yahoo.it <mailto:giuseppe_ar...@yahoo.it>>> wrote: > > >>> > > >>> > > >>> Hi all, > > >>> I attached some screenshots of a new proposal for tooltips. > Before > > >>> applying changes OJ NB I would like your opinion about. > > >>> The tooltips are reduced to 3 lines, except WFS (see later) > > >>> > > >>> *a) layers with datasource and no unsaved change* > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> *b) layers with datasource but with unsaved change * > > >>> > > >>> > > >>> > > >>> > > >>> *c) Layer with no datasource* > > >>> > > >>> > > >>> *d) Rendered Image Layer * > > >>> > > >>> > > >>> *e) WMS layer* > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> *f) Sextante Raster Image Layer*____ > > > > >>> Some notes: > > >>> Vector layers: > > >>> Blu color will show if a layer (with datasource) has been > modified. > > >>> Red color will advise that the layer has no datasource > > >>> > > >>> WMS: The 3 lines shows Layer name, URL and CRS > > >>> > > >>> WFS: (not shown) the lines will be 4: layer name, URL, CRS > and Number of > > >>> features > > >>> > > >>> Multiple rendered Image loaded via Image Layer manager: > actually the > > >>> second line will show only a "Multiple source" text. In the > future I would > > >>> like to add the list of the loaded files. Number of items > shows the number > > >>> of files > > >>> > > >>> Sextante Layer: it is basically the same as Rendered Image > (3 lines, > > >>> layer, file, number of items. I would like to change the > icon. Both icons > > >>> are very similar > > >>> > > >>> > > >>> > > >>> > ------------------------------------------------------------------------------ > > >>> Dive into the World of Parallel Programming The Go Parallel > Website, > > >>> sponsored > > >>> by Intel and developed in partnership with Slashdot Media, > is your hub > > >>> for all > > >>> things parallel software development, from weekly thought > leadership > > >>> blogs to > > >>> news, videos, case studies, tutorials and more. Take a look > and join the > > >>> conversation now. http://goparallel.sourceforge.net/ > > >>> > > >>> _______________________________________________ > > >>> Jump-pilot-devel mailing list > > >>> Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > <mailto:Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net>> > > >>> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > >>> > > >>> > > >>> > > >>> > > >>> > ------------------------------------------------------------------------------ > > >>> Dive into the World of Parallel Programming The Go Parallel > Website, > > >>> sponsored > > >>> by Intel and developed in partnership with Slashdot Media, > is your hub > > >>> for all > > >>> things parallel software development, from weekly thought > leadership > > >>> blogs to > > >>> news, videos, case studies, tutorials and more. Take a look > and join the > > >>> conversation now. http://goparallel.sourceforge.net/ > > >>> _______________________________________________ > > >>> Jump-pilot-devel mailing list > > >>> Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > <mailto:Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net>> > > >>> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > >>> > > >>> > > >> > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > Dive into the World of Parallel Programming The Go Parallel > Website, sponsored > > > by Intel and developed in partnership with Slashdot Media, is > your hub for all > > > things parallel software development, from weekly thought > leadership blogs to > > > news, videos, case studies, tutorials and more. Take a look > and join the > > > conversation now. http://goparallel.sourceforge.net/ > > > > > > > > > > > > _______________________________________________ > > > Jump-pilot-devel mailing list > > > Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > <mailto:Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net>> > > > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > > > > > > ------------------------------------------------------------------------------ > > Dive into the World of Parallel Programming The Go Parallel > Website, sponsored > > by Intel and developed in partnership with Slashdot Media, is > your hub for all > > things parallel software development, from weekly thought > leadership blogs to > > news, videos, case studies, tutorials and more. Take a look and > join the > > conversation now. http://goparallel.sourceforge.net/ > > _______________________________________________ > > Jump-pilot-devel mailing list > > Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > <mailto:Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net>> > > > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel____ > > > > __ __ > > > > __ __ > > > > > > > ------------------------------------------------------------------------------ > > Dive into the World of Parallel Programming The Go Parallel > Website, sponsored > > by Intel and developed in partnership with Slashdot Media, is > your hub for all > > things parallel software development, from weekly thought > leadership blogs to > > news, videos, case studies, tutorials and more. Take a look and > join the > > conversation now. http://goparallel.sourceforge.net/ > > _______________________________________________ > > Jump-pilot-devel mailing list > > Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > <mailto:Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net>> > > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > Dive into the World of Parallel Programming The Go Parallel Website, > sponsored > > by Intel and developed in partnership with Slashdot Media, is your hub > for all > > things parallel software development, from weekly thought leadership > blogs to > > news, videos, case studies, tutorials and more. Take a look and join the > > conversation now. http://goparallel.sourceforge.net/ > > > > > > > > _______________________________________________ > > Jump-pilot-devel mailing list > > Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, > sponsored > by Intel and developed in partnership with Slashdot Media, is your hub > for all > things parallel software development, from weekly thought leadership > blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > <mailto:Jump-pilot-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > > > > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
