Re: [JPP-Devel] SVN: [5261] core/trunk/src

whoops, forgot to commit the fix for OpenFileWizard. it's a little different, so i committed it Mike's change. ..ede On 16.12.2016 08:43, jump-pilot-...@lists.sourceforge.net wrote: > Revision: 5261 > http://sourceforge.net/p/jump-pilot/code/5261 > Author: michaudm > Date:

Re: [JPP-Devel] SVN: [5262] core/trunk

hey Mike, On 16.12.2016 09:03, jump-pilot-...@lists.sourceforge.net wrote: > +if ((int)c < 20 && c != '\t' && c != '\n' && c != 'r') { > +sb.replace(t, t + 1, ""); > +} c!='r' should probably be '\r' ? it would be cleaner to use an xml library to escape

Re: [JPP-Devel] Save View As Raster is broken

fixed in r5258.. ede On 15.12.2016 11:22, edgar.sol...@web.de wrote: > hey guys, > > seems like an oversight in the raster export code. it is perfectly valid for > JFC.getSelectedFile() to return NULL if there was nothing selected, which is > the case when using the file chooser for the first

Re: [JPP-Devel] Save View As Raster is broken

hey guys, seems like an oversight in the raster export code. it is perfectly valid for JFC.getSelectedFile() to return NULL if there was nothing selected, which is the case when using the file chooser for the first time. not sure why that worked all this time ;) but it's easily fixable. will

Re: [JPP-Devel] Roadmatcher for OJ 1.10

On 12.12.2016 22:00, Michaël Michaud wrote: > Hi Ede, > > No problem, if you revert the code in the core, I'll revert the code in > Roadmatcher. done > But maybe changing back the method signature will now break the core... > let's see. nP.. got that covered.. ede

Re: [JPP-Devel] Roadmatcher for OJ 1.10

On 07.12.2016 20:46, Michaël Michaud wrote: > a third problem arose with WorkbenchContext#getErrorHandler where you > changed the return type from ErrorHandler to ErrorHandler2 > I thought this is OK (called covariance isn't it), but fort a reason, I > get compilation errors. Maybe you know why.

Re: [JPP-Devel] Roadmatcher for OJ 1.10

can you quickly elaborate what broke it? ..ede On 07.12.2016 08:52, Michaël Michaud wrote: > Hi, > > I just upgraded RoadMatcher so that it is compatible with future OJ1.10 > (need last NB of OJ) > > https://sourceforge.net/projects/jump-pilot/files/OpenJUMP_plugins/More%20Plugins/ > >

[JPP-Devel] Fwd: Re: Fwd: Re: Java codes in OpenJUMP which are not under GNU or any other public licence

for reference here's the answer from Ugo.. ede Forwarded Message Subject:Re: Fwd: Re: [JPP-Devel] Java codes in OpenJUMP which are not under GNU or any other public licence Date: Mon, 5 Dec 2016 18:38:36 +0100 From: Ugo Taddei To: Edgar Soldin <

Re: [JPP-Devel] Sextante

as the sextante binding source is in svn, let me have a try at that initialization. i think, i can simplify that somewhat and make sure it runs wherever it is placed. might take until the weekend though. ..ede On 06.12.2016 15:40, Giuseppe Aruta wrote: > Hi Ede, > can you check the new

Re: [JPP-Devel] Sextante

Peppe also sextante does not seem to work, i suggest you simply detect if the path's exist and set them properly. errors are : 1. for the help java.lang.NullPointerException at es.unex.sextante.gui.help.SextanteHelpWindow.fillTree(SextanteHelpWindow.java:274) at

Re: [JPP-Devel] Sextante

Peppe, tried the latest, this is what shows when verbosity is '-v info' starting Sextante initialization >> Sextante not initialized! Check for problems with Sextante initialization, path for libs and resources: E:\proj_oj-core_svn-4.4\lib\ext\sextante Check if image 'terminal.png' exist Check

Re: [JPP-Devel] Sextante

go Peppe go :).. ede On 05.12.2016 15:26, Giuseppe Aruta wrote: > Ede, > OK, I uderstood > we need all the info back. It seems correct to control all the loading > process on ide > I will try to reenable it > > Peppe > > > > 2016-12-05 12:01 GMT+01:00 : > >> Peppe, >> >>

Re: [JPP-Devel] Sextante

Peppe, there was already a workaround to run sextante binding in eclipse, that you seem to have deactivated. Stefan added it in the past, it's output was starting Sextante initialization >> Sextante jar folder: E:\proj_oj-core_svn-4.4/lib/ext/sextante Sextante not initialized! Check for

Re: [JPP-Devel] Sextante

hey Peppe, running OJ from eclipse gives me a NPE during startup now java.lang.NullPointerException at es.unex.sextante.core.AlgorithmsAndResources.addAlgorithmsAndPropertiesFromFolder(AlgorithmsAndResources.java:143) at

Re: [JPP-Devel] [jump-pilot:feature-requests] #237 LayerView/AttributeTable selection synchronization

On 04.12.2016 19:37, Michaël Michaud wrote: > I know you're more familiar with UI > and KeyEvents handling. at least i should. OJ plugin shortcuts are my brainchild, pretty much completely.. ede -- Check out the

Re: [JPP-Devel] [jump-pilot:feature-requests] #237 LayerView/AttributeTable selection synchronization

hey Mike, saw your mail. will come back to you wrt. #440.. ede On 04.12.2016 19:24, michael michaud wrote: > See elso bug #440 > >

Re: [JPP-Devel] Java codes in OpenJUMP which are not under GNU or any other public licence

i'll CC Lat-Lon, as the latest contact to the original author Ugo Taddei . @Lat-lon: do you guys have a more recent mail address for Ugo Taddei? thank you! @Peppe: interesting stuff! the license header

Re: [JPP-Devel] SVN: [5237] core/trunk/src

On 01.12.2016 22:44, jump-pilot-...@lists.sourceforge.net wrote: > Revision: 5237 > http://sourceforge.net/p/jump-pilot/code/5237 > Author: michaudm > Date: 2016-12-01 21:44:25 + (Thu, 01 Dec 2016) > Log Message: > --- > Revert visibility of some methods to public as

Re: [JPP-Devel] Join table can go to eternal loop

"ignore nulls" check box." enabled by default, sounds good to me. there might be corner cases where null is a valid value in some dataset somehow ;) ..ede On 01.12.2016 23:55, Michaël Michaud wrote: > OK, > > With two layers including 1000 features with nulls, it will create a > layer with 1

Re: [JPP-Devel] SVN: [5231] core/trunk/etc/readme.txt

Peppe, close, but not quite correct. please check the format of the listing, it's mentioned on top of the listing Name - License Name - corresponding file in license/ folder look at the other entries for orientation ;) also you probably mean "provided". ..ede On 28.11.2016 21:15,

Re: [JPP-Devel] SVN: [5226] core/trunk/lib/plus/sextante/sextante_new_algorithms.jar

hey Peppe, please add the new files and license to etc/readme.txt as well.. thx ede On 28.11.2016 17:12, jump-pilot-...@lists.sourceforge.net wrote: > Revision: 5226 > http://sourceforge.net/p/jump-pilot/code/5226 > Author: ma15569 > Date: 2016-11-28 16:12:59 + (Mon, 28 Nov

Re: [JPP-Devel] @Ede. Reorganize Sextante help folder

hey Peppe, sounds good to me. make it so :).. ede PS: https://www.youtube.com/watch?v=-ZxHAZChcYU On 28.11.2016 17:20, Giuseppe Aruta wrote: > Hi Ede > I am going to upgrade Sextante with a new OJ binding that solved some > problems: one of them is the help framework which requires a new folder

Re: [JPP-Devel] Add SRID and units to Task

Manfred, hires versions of both are available in our svn https://sourceforge.net/p/jump-pilot/code/HEAD/tree/core/trunk/logo/ & https://sourceforge.net/p/jump-pilot/code/HEAD/tree/core/trunk/icon/ . as long as they are used in conjunction with OJ, you are free to use them as they are. feel

Re: [JPP-Devel] SVN: [5218] core/trunk

On 23.11.2016 23:20, Michaël Michaud wrote: > Hey, > > Remember we already had this kind of problem in the past. yeah, it looked vaguely familiar. i am getting old ;) > Is it related to the use of Bat_to_Exe converter ? jepp, it is! anyway, i finally got fed up and hacked a minimal C starter

Re: [JPP-Devel] next OJ release

Landon, no hurry. i myself will need at least until the end of the year to finish up my construction site. do you still have your svn access? if so, you can simply commit and snapshots will be generated automatically, being the "pre-release" builds until we freeze the svn and release the new

Re: [JPP-Devel] SVN: [5193] core/trunk/src

makes sense. thx ede On 18.11.2016 17:48, Michaud Michael wrote: > Hi Ede > > > > if (compressedEntry == null) { > } > else if () { > // Here I suppose compressedEntry is not null - am I right ? > } > Michaël > > > > > > > >> Message du 18/11/16 13:45 >> De : edgar.sol...@web.de >>

Re: [JPP-Devel] SVN: [5193] core/trunk/src

hey Mike, see below On 18.11.2016 13:38, jump-pilot-...@lists.sourceforge.net wrote: > Modified: core/trunk/src/com/vividsolutions/jump/io/CompressedFile.java > === > --- core/trunk/src/com/vividsolutions/jump/io/CompressedFile.java

Re: [JPP-Devel] oj_windows launchers

On 17.11.2016 08:50, Michaël Michaud wrote: > Hi Ede, > > This week, several co-workers have had problems with their java installation > after an automatic update on their windows machine (problems probably related > to the enterprise update policy, not the standard windows update). > > On

Re: [JPP-Devel] SVN: [5190] core/trunk

tried it on my dual monitor system, seems to be fixed. ..ede On 15.11.2016 23:15, jump-pilot-...@lists.sourceforge.net wrote: > Revision: 5190 > http://sourceforge.net/p/jump-pilot/code/5190 > Author: michaudm > Date: 2016-11-15 22:15:19 + (Tue, 15 Nov 2016) > Log Message: >

Re: [JPP-Devel] SVN: [5185] core/trunk/src/com/vividsolutions/jump/workbench/ui/ LayerNameRenderer.java

eler. > > Michaël > > > Le 15/11/2016 à 21:49, Rahkonen Jukka (MML) a écrit : >> Good idea. How about having an option to rename the columns to be exported >> by the same? Would be handy for example when exporting columns with long >> names into shapefiles

Re: [JPP-Devel] SVN: [5185] core/trunk/src/com/vividsolutions/jump/workbench/ui/ LayerNameRenderer.java

ok. A. equals B. there, i mean A. flexible B. reusable.. ede On 15.11.2016 21:21, edgar.sol...@web.de wrote: > maybe a panel to select the columns to be exported for the selected format > would be A. reusable B. fitting for several formats (eg. csv, json). > > ..ede > > On 15.11.2016 18:44,

Re: [JPP-Devel] Invalid GeoJSON if no attributes

would you mind packing it and maybe some summer heat on the side as well and send it to cologne? ;).. ede de la Capital de los tontos On 15.11.2016 14:29, Stefan Steiniger wrote: > ede, got some sun for you on my metro ride to work. > > stefan > > -- Originalnachricht -- > *Von: * >

Re: [JPP-Devel] Invalid GeoJSON if no attributes

should be fixed in r5189 ..ede On 15.11.2016 12:27, edgar.sol...@web.de wrote: > On 15.11.2016 12:02, Rahkonen Jukka (MML) wrote: >> Hi, >> >> One closing "}" seems to be missing. There is EPSG:0"}}} but should be one >> more. Otherwise validates in jsonling.com and in geojsonlint.com. > >

Re: [JPP-Devel] Invalid GeoJSON if no attributes

On 15.11.2016 12:02, Rahkonen Jukka (MML) wrote: > Hi, > > One closing "}" seems to be missing. There is EPSG:0"}}} but should be one > more. Otherwise validates in jsonling.com and in geojsonlint.com. whooops a typo ;) > { > "type": "FeatureCollection", > > "features": [ > { "type":

Re: [JPP-Devel] SVN: [5185] core/trunk/src/com/vividsolutions/jump/workbench/ui/ LayerNameRenderer.java

Jukka, nothing to worry, my mind was w/ GeoJSON still and the only possibility to add an empty geom there is to use GeometryCollection because of the constraints i described. my bad ..ede On 15.11.2016 11:16, Rahkonen Jukka (MML) wrote: > Hi, > > What do you mean? You did lot of work with

Re: [JPP-Devel] SVN: [5185] core/trunk/src/com/vividsolutions/jump/workbench/ui/ LayerNameRenderer.java

GeometryCollection is afaik the only possibility to have an empty geometry as all other geom types require either coordinates or sub geoms per definition. ..ede On 15.11.2016 11:06, Rahkonen Jukka (MML) wrote: > Hi, > > DB Query plugin is attaching a fake GEOMETRYCOLLECTION EMPTY to all the

Re: [JPP-Devel] Invalid GeoJSON if no attributes

Jukka, please try r5188.. ede On 15.11.2016 10:31, edgar.sol...@web.de wrote: > from http://geojson.org/geojson-spec.html > " > A GeoJSON object with the type "Feature" is a feature object. > > A feature object must have a member with the name "geometry". The value of > the geometry member is

Re: [JPP-Devel] Invalid GeoJSON if no attributes

from http://geojson.org/geojson-spec.html " A GeoJSON object with the type "Feature" is a feature object. A feature object must have a member with the name "geometry". The value of the geometry member is a geometry object as defined above or a JSON null value. A feature object must have a

Re: [JPP-Devel] SVN: [5185] core/trunk/src/com/vividsolutions/jump/workbench/ui/ LayerNameRenderer.java

i guess the cleanest solution would be a new layer class eg. DataLayer, that simply does not allow adding/editing geometries or does not even have a geometry attribute. in the 2nd case you would probably need a new featurecollection w/o a geometry column as well and the whole thing would throw

Re: [Duplicity-team] [Question #404018]: Forced disconnect of my internet connection during backup

Nils, you should be able to generate patches and send them to the mailing list, that should suffice. ..ede/duply.net On 13.11.2016 21:27, nils wrote: > Question #404018 on Duplicity changed: > https://answers.launchpad.net/duplicity/+question/404018 > > Status: Solved => Open > > nils is

Re: [JPP-Devel] SVN: [5185] core/trunk/src/com/vividsolutions/jump/workbench/ui/ LayerNameRenderer.java

thanks.. how about implementing the caching/listener approach if you like to have icon? ..ede On 13.11.2016 18:57, Giuseppe Aruta wrote: > Ok Ede, I didn't know it. I will revert the change. > Thanks again > Peppe > > Il 13/Nov/2016 18:48, ha scritto: > >> Peppe, >> >>

Re: [JPP-Devel] SVN: [5185] core/trunk/src/com/vividsolutions/jump/workbench/ui/ LayerNameRenderer.java

Peppe, NACK.. this is going to get very slow for huge datasets containing empty geoms only, as it is run on every redraw of the layer tree. please cache the state and use a layer change listener or else users will complain about a frozen OJ some time in the future and we will have a hard time

Re: [JPP-Devel] How to activate ECW/JP2?

On 07.10.2016 12:29, edgar.sol...@web.de wrote: > On 07.10.2016 12:21, Rahkonen Jukka (MML) wrote: >> Mail reason for potentially keeping the ECW/JP2 driver: it is faster. At >> least I am remembering it was fast and therefore I tried to test it again. >> There is rather a long lag in opening

[JPP-Devel] new SaveWizard, open issues

hey All, wrt. the topic above. what do you still expect from it to replace the SaveDatasetAsPlugin completely. i am aware of 1. no GML2.0 template support (do we actually still need that writer? what is the template for actually?) 2. EnableCheck support needed within the Wizard to en/disable

[JPP-Devel] next OJ release

hey All, we should start cleaning and finishing as I would like to release/prepare during the holidays as it seems to become traditional at least w/ me. are there any bigger construction sites still pending? from my side, there are 1. i am going to polish the new SaveWizard. i will write a

Re: [JPP-Devel] SVN: [5171] plug-ins/SextantePlugIn

hey Peppe, any specific reason to make this plugin threaded but not using threads? ..ede On 08.11.2016 16:28, jump-pilot-...@lists.sourceforge.net wrote: > Revision: 5171 > http://sourceforge.net/p/jump-pilot/code/5171 > Author: ma15569 > Date: 2016-11-08 15:28:51 + (Tue, 08

Re: [JPP-Devel] SVN: [5054] core/trunk

right. should be fixed in r5168.. thx ede On 06.11.2016 17:34, Michaël Michaud wrote: > Hi Ede, > > When starting OpenJUMP, I now get the following exception from the console : > > java.lang.NullPointerException > at >

[JPP-Devel] overwrite warning w/ SaveLayersWithoutDataSourcePlugIn

hey All, while playing w/ the above plugin i noticed that it overwrites w/o any warning. that feels wrong. what do you say? ..ede -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi

Re: [JPP-Devel] DataSource URI_KEY vs FILE

On 05.10.2016 09:05, Michaël Michaud wrote: > Hi Ede, > > I made a quick fix to solve #431 but I wonder if it should'nt be fixed more > deeply. > > The bug has been introduced with the addition of DataSource.URI_KEY. > > It seems that for file based sources, we now have to keys to define the

Re: [JPP-Devel] Can't edit the schema of some layers

On 04.11.2016 15:19, edgar.sol...@web.de wrote: > On 04.11.2016 14:43, Rahkonen Jukka (MML) wrote: >> > Yes, when reading GeoJSON it is OK to create a column as the first met >> > not-null datatype and populate the column with a mixture of proper values >> > and null values. > > ok, i'll patch

Re: [JPP-Devel] AbstractPlugIn and EnableCheck

On 06.11.2016 00:02, Michaël Michaud wrote: > Hi Ede, hey Mike, > A question about plugin design. > > In 2012, you added both > - an EnableCheck interface implemented by AbstractPlugIn > - an implementation of this interface in AbstractPlugIn which retrieve > older createEnableCheck method by

Re: [JPP-Devel] Can't edit the schema of some layers

On 04.11.2016 14:43, Rahkonen Jukka (MML) wrote: > Yes, when reading GeoJSON it is OK to create a column as the first met > not-null datatype and populate the column with a mixture of proper values and > null values. ok, i'll patch the GeoJSON reader accordingly. > JSON allows also that

Re: [JPP-Devel] Can't edit the schema of some layers

thx Mike that goes for writing JSON, but what about reading. is it ok to create attribute columns that contain NULL values _and_ proper numbers, strings, boolean values etc.? ..ede On 04.11.2016 13:35, Michaël Michaud wrote: > Hi Ede, > > As stated in this discussion, I think that defining a

Re: [JPP-Devel] Can't edit the schema of some layers

Mike, any opinion on the below? ..ede On 03.11.2016 16:20, edgar.sol...@web.de wrote: > just for completeness. does the same count for writing GeoJSON? obviously > GDAL does it, but could you test w/ some other reader to doublecheck null > mixed columns? > > ..ede > > On 03.11.2016 16:16,

Re: [JPP-Devel] Memory issue with writing to PostGIS and with reading too

On 04.11.2016 08:40, Rahkonen Jukka (MML) wrote: > That computer has 8 GB total memory and perhaps 6 GB available for OpenJUMP. what does it say under About->Info->MaxMemory ? which revision do you use? ..ede --

Re: [JPP-Devel] Can't edit the schema of some layers

just for completeness. does the same count for writing GeoJSON? obviously GDAL does it, but could you test w/ some other reader to doublecheck null mixed columns? ..ede On 03.11.2016 16:16, Rahkonen Jukka (MML) wrote: > I tested JML with Boolean and date, parses nulls OK, I believe no

Re: [JPP-Devel] Can't edit the schema of some layers

and it parses Double values too. so any exceptions needed or none at all? ..ede On 03.11.2016 16:06, edgar.sol...@web.de wrote: > only for these two types or for Boolean as well? > > ..ede > > On 03.11.2016 15:53, Rahkonen Jukka (MML) wrote: >> Hi, >> >> JML reader accepts nulls in strings and

Re: [JPP-Devel] Can't edit the schema of some layers

only for these two types or for Boolean as well? ..ede On 03.11.2016 15:53, Rahkonen Jukka (MML) wrote: > Hi, > > JML reader accepts nulls in strings and longs (try with the attached file), I > would say that GeoJSON driver should do the same. > > -Jukka- > > edgar.sol...@web.de

Re: [JPP-Devel] Can't edit the schema of some layers

Mike, Jukka, so what do you guys say. should the GeoJSON reader accept Long/null mixed columns as Long and do the same for the other attribute types or enforce these columns to be of type String as it is implemented now. ..ede On 03.11.2016 13:20, Rahkonen Jukka (MML) wrote: > OpenJUMP

Re: [JPP-Devel] Can't edit the schema of some layers

Jukka, please try the latest snapshot from a minute ago. generally the reader assumes that NULL is a specific type. it looks like OJ tolerates numerical columns with NULL values. is that standard, should i modify the reader accordingly? is it a general rule for all attribute types? ..ede On

Re: [JPP-Devel] Can't edit the schema of some layers

i see the issue. there is one "keskikorkeus" being NULL forcing the whole attribute column to become String. of course this is a bug in the GeoJSON reader and i'll fix it. ..ede On 03.11.2016 12:24, Rahkonen Jukka (MML) wrote: > By taking the big dataset that I had originally in JML format and

Re: [JPP-Devel] Can't edit the schema of some layers

how did you create it? manually by editing the geoJson file with a text editor? ..ede On 03.11.2016 12:09, Rahkonen Jukka (MML) wrote: > Hi, > > I managed to create test data with only 100 features > http://latuviitta.org/downloads/100.json > > For testing just open and try to edit and save

Re: [JPP-Devel] Fwd: [jump-pilot:bugs] #438 Close openjump without saving project

nice :).. ede On 02.11.2016 19:48, Michaël Michaud wrote: > Thanks, > > Should be fine now ;-) > > Michaël > > > Le 02/11/2016 à 16:43, edgar.sol...@web.de a écrit : >> Mike, >> >> i just refined the errorhandling r5142 and fixed the NPE you mentioned. thx >> for pointing that out! ..ede >>

Re: [JPP-Devel] Can't edit the schema of some layers

is this sensitive data, or why did you write "So unfortunately I can’t provide with test data." ..ede On 02.11.2016 17:16, edgar.sol...@web.de wrote: > Jukka, > > can you send me a small GeoJSON example file to replicate your issue? ..ede > > On 02.11.2016 17:12, Rahkonen Jukka (MML) wrote: >>

Re: [JPP-Devel] Can't edit the schema of some layers

Jukka, can you send me a small GeoJSON example file to replicate your issue? ..ede On 02.11.2016 17:12, Rahkonen Jukka (MML) wrote: > Hi, > > > > I opened some data from GeoJSON and I can’t edit the schema. Apply changes > yields just an error message. However, if I save the data into JML

Re: [JPP-Devel] Fwd: [jump-pilot:bugs] #438 Close openjump without saving project

Mike, i just refined the errorhandling r5142 and fixed the NPE you mentioned. thx for pointing that out! ..ede On 02.11.2016 15:02, Michaud Michael wrote: > OK, I'll check your change tonight, thanks, > > > > Michaël > > De : edgar.sol...@web.de > > Date d'envoi : mercredi 2 novembre 2016

Re: [JPP-Devel] Fwd: [jump-pilot:bugs] #438 Close openjump without saving project

Mike, you mean WorkbenchFrame.log(...)? the missing t should be the reason that it does not print a stack. i guess what i wanted to achieve was some backward compatible info logging. level info shouldn't print stacks, so it is ignored. but let me fix it as ignore or use it, depending on the

Re: [JPP-Devel] SVN: [5137] core/trunk

On 01.11.2016 14:57, jump-pilot-...@lists.sourceforge.net wrote: > Revision: 5137 > http://sourceforge.net/p/jump-pilot/code/5137 > Author: michaudm > Date: 2016-11-01 13:57:35 + (Tue, 01 Nov 2016) > Log Message: > --- > Fix #438 Exception while saving the project

Re: [JPP-Devel] Sextante bugs for next OJ realize.

let's summarize the Changelog (have to do it for the release anyway) and then decide what's it going to be. not much alternatives here 2.0 or 1.10 :) ..ede On 24.10.2016 23:11, Michaël Michaud wrote: > Hi, > > Yes, I think we should release a new version before the end of 2016. > > I would say

Re: [LEDE-DEV] Actual community change and additional developers compared to OpenWrt

On 24.10.2016 19:26, Val Kulkov wrote: > Hi Jo, > Part of the problem, I think, is the lack of clear and consistent (and visible) governance and communication makes the project unappealing for companies to be interested in paying developers to work on either. It's not

Re: [LEDE-DEV] [PATCH v4] base-files: Ensure reset only works if an overlay exists

On 23.10.2016 23:42, edgar.sol...@web.de wrote: > On 23.10.2016 21:30, Bastian Bittorf wrote: >> * Chris Blake [23.10.2016 21:10]: >>> +OVERLAY="$( grep ' /overlay ' /proc/mounts 2>/dev/null )" >> >> whats the reason for the 2>...? >> > > for the corner case that the

Re: [LEDE-DEV] [PATCH v4] base-files: Ensure reset only works if an overlay exists

On 23.10.2016 21:30, Bastian Bittorf wrote: > * Chris Blake [23.10.2016 21:10]: >> +OVERLAY="$( grep ' /overlay ' /proc/mounts 2>/dev/null )" > > whats the reason for the 2>...? > for the corner case that the error message might contain ' /overlay' ? just a guess..

Re: [JPP-Devel] About turning non-visible layer into non-editable

good point. so mainly we are talking prohibiting CursorTools to edit invisible layers. maybe we should think smaller and just change the way CursorTools determine the layer to edit. ..ede On 19.10.2016 11:20, Rahkonen Jukka (MML) wrote: > Hi, > > Trying to think how we actually edit layers: >

Re: [JPP-Devel] About turning non-visible layer into non-editable

Mike, had a quick look. simplest approach might be just editing AbstractLayerable.isEditable() to always return boolean sum of editable && visible, no? all layerables i know are based on AbstractLayerable. plugins probably all use TreeLayerNamePanel.chooseEditableLayer() *but* do not have to.

Re: [JPP-Devel] About turning non-visible layer into non-editable

On 18.10.2016 14:56, Rahkonen Jukka (MML) wrote: > Hi, > > > > I agree that it is logically good that non-visible layer is not editable > because I can’t imagine a real world use case where it would be better to > create features without seeing the other features of the layer. However, >

Re: [JPP-Devel] #431 Save project with unsaved layers

Mike, still trying to find the time to check and fix the underlying issue in JFCWithEnter properly.. please be patient ede On 17.10.2016 22:50, Michaël Michaud wrote: > Hi Ede, > > Let me know if you find something better to do with > > #431 Save project with unsaved layers > > Michaël > >

Re: [JPP-Devel] GvSIG better with GDAL than ImageIO-ext?

On 18.10.2016 09:52, Rahkonen Jukka (MML) wrote: > Hi, > > > > I installed GvSIG 2.3.0.2447 final 64-bit on Windows. It opens both ECW and > JPEG2000 files very fast. GvSIG seems to be using the same GDAL binaries from > gisinternals.com than Ede has packed for OJ. Difference seems to be

Re: [JPP-Devel] Fwd: Error on Sextante Raster Layer on OJ NB

i checked with your example 'skeenah_dem_10m.tif' . seems like the devs changed something between 0.1.13(Nov15) and 0.1.14(Jun16) https://github.com/geosolutions-it/imageio-ext/commits/master/plugin/tiff that breaks reading that file. we can of course easily downgrade this ImageIO-Ext plugin

Re: [JPP-Devel] Fwd: Error on Sextante Raster Layer on OJ NB

it should not be missing. i used the more recent java bindings from gdal-2.1.0.jar instead. https://sourceforge.net/p/jump-pilot/code/HEAD/tree/core/trunk/lib/imageio-ext/ but heck, we can of course roll that back to the original bindings released together w/ ImageIO-Ext. :) ..ede On

Re: [JPP-Devel] Fwd: Error on Sextante Raster Layer on OJ NB

if you'd like to use your local GDAL you will have to run OJ with a 32bit java. you are right, it does not seem to detect GDAL. ..ede On 14.10.2016 17:06, Giuseppe Aruta wrote: > Yes I do. I installed and defined class paths a day before. Currently my > machine works with Gdal 1.11.4/32bit

Re: [JPP-Devel] Fwd: Error on Sextante Raster Layer on OJ NB

then probably the GDAL jni libs are not in your path. ok, forget it. if you want try you should be able to use the GDAL provided and as described here http://ojwiki.soldin.de/index.php?title=Working_with_Raster#GDAL_support_.28Windows.2C_Linux_only.29 ..ede On 14.10.2016 17:18, Giuseppe

Re: [JPP-Devel] Fwd: Error on Sextante Raster Layer on OJ NB

maybe a bug in the updated ImageIO-Ext.. did you intend to use _this_ reader? i can't see that the class in the stack was changed recently though https://github.com/geosolutions-it/imageio-ext/tree/master/plugin/tiff/src/main/java/it/geosolutions/imageio/plugins/tiff the ImageIO-Ext TIFF

Re: [JPP-Devel] How to activate ECW/JP2?

On 10.10.2016 08:43, Rahkonen Jukka (MML) wrote: > It is only the 41 seconds wait with initial opening. I don't believe that > the lag comes from the ECW/JPEG2000 SDK because it is the same, nor from GDAL > because QGIS opens images fast. We do not have much left and it must be > either

Re: [JPP-Devel] How to activate ECW/JP2?

Jukka, On 07.10.2016 12:29, edgar.sol...@web.de wrote: > On 07.10.2016 12:21, Rahkonen Jukka (MML) wrote: >> Mail reason for potentially keeping the ECW/JP2 driver: it is faster. At >> least I am remembering it was fast and therefore I tried to test it again. >> There is rather a long lag in

Re: [JPP-Devel] SVN: [5060] plug-ins/SextantePlugIn

hey Peppe, your new sextante binding seems to be compiled for java 1.8 . it wont run with java 1.7 anymore. please check and retry.. ede On 09.10.2016 07:57, jump-pilot-...@lists.sourceforge.net wrote: > Revision: 5060 > http://sourceforge.net/p/jump-pilot/code/5060 > Author:

Re: [JPP-Devel] Problems on saving Sextante plugin

Peppe & all, an error like the below can happen on sf.net. sometimes they have technical difficulties or are recovering from some outage and the symptom for that is the impossibility to commit to svn, often w/ some error wrt. to insufficient authentication. usually that disappears over time,

Re: [JPP-Devel] SVN: [5056] core/trunk

hey Peppe, looks like you deleted some of Mike's Changelog entries.. ede On 08.10.2016 18:10, jump-pilot-...@lists.sourceforge.net wrote: > Revision: 5056 > http://sourceforge.net/p/jump-pilot/code/5056 > Author: ma15569 > Date: 2016-10-08 16:10:24 + (Sat, 08 Oct 2016) > Log

Re: [JPP-Devel] SVN: [5054] core/trunk

hey Mike, that looks wrong. without JFCWithEnterAction you may not finish your input with the enter key. what was the issue? ..ede On 07.10.2016 09:06, jump-pilot-...@lists.sourceforge.net wrote: > Revision: 5054 > http://sourceforge.net/p/jump-pilot/code/5054 > Author: michaudm >

Re: [JPP-Devel] How to activate ECW/JP2?

On 07.10.2016 12:21, Rahkonen Jukka (MML) wrote: > Mail reason for potentially keeping the ECW/JP2 driver: it is faster. At > least I am remembering it was fast and therefore I tried to test it again. > There is rather a long lag in opening JPEG2000 images through imageio-ext + > GDAL while

Re: [JPP-Devel] How to activate ECW/JP2?

still better than the native ECW reader in PLUS, which is limited java 32bit on MacOSX and Windows. as far as i am aware there is no 32bit java avail anymore for MacOSX. on Linux and MacOSX users may install GDAL in the system and that should work as well if we deliver it to be placed under

Re: [JPP-Devel] How to activate ECW/JP2?

yeah, something is fishy there. tried it for 5min myself lately, not sure whats wrong, but on the other hand, why not simply remove it in favor of GDAL? ..ede On 07.10.2016 09:28, Rahkonen Jukka (MML) wrote: > Hi, > > > > I am running r5052 Plus with jre8, 32-bit. I guess that I should have

Re: [JPP-Devel] jp2 driver

wrong folder. read the INSTALL-gdal-win-x86x64-2.1.0stable-20160516.txt in the zip file. no wonder no one is using it if even you fail to install it ;).. ede On 06.10.2016 16:05, Rahkonen Jukka (MML) wrote: > Ok, found it: by starting with JAVA_BIN=java and having a look on the last > lines

Re: [JPP-Devel] jp2 driver

Jukka & all, can you please test if the new Imageio-Ext & GDAL 2.1.0 work to your satisfaction? i opened ECW & JP2 and it worked for me. you'll need OJ r5052+ https://sourceforge.net/projects/jump-pilot/files/OpenJUMP_snapshots/ &

Re: [JPP-Devel] SVN: [5047] core/trunk

On 06.10.2016 13:51, Michaël Michaud wrote: > Anyway, having both properties is very error prone. agreed. but you see, the old Readers/Writers used it, while our Datasource framework doesn't. so the logical point to insert the legacy compatibility code would be where readers/writers are

Re: [JPP-Devel] SVN: [5052] core/trunk/src

hey Mike, how about simply adding it to ReaderWriterFileDataSource.getDriverProperties() ? a uri should probably be checked for a file:// prefix before creating a file path out of it. ..ede On 06.10.2016 13:46, jump-pilot-...@lists.sourceforge.net wrote: > Revision: 5052 >

Re: [JPP-Devel] jp2 driver

hey Jukka, On 04.10.2016 13:27, Rahkonen Jukka (MML) wrote: > Current GDAL version is 2.1.1. Yes, it is worth an update. http://www.gisinternals.com/release.php only holds 2.1.0, so i used that. or would you advise to use the daily builds? ..ede

Re: [JPP-Devel] SVN: [5047] core/trunk

do you agree with my assessment below?.. ede On 06.10.2016 13:00, Michaël Michaud wrote: > Hi, > > Yes, seems that I've broken something, > > Michaël > > > Le 06/10/2016 à 12:07, edgar.sol...@web.de a écrit : >> hey Mike, >> >> is it possible you broke zip reloading on project opening with

Re: [JPP-Devel] SVN: [5047] core/trunk

hey Mike, is it possible you broke zip reloading on project opening with your commit? haven't downloaded it yet and am not sure i like the changes. many changes always equals a higher probability to break something. why couldn't you simply create the "missing" property directly before the file

Re: [JPP-Devel] Sextante

On 05.10.2016 16:40, Brian M Hamlin wrote: > > Hi All - > > sorry to lurk here.. but.. I am very alarmed at this email. > You really do not want to lose your source code. > Second, the ability to build from source.. no worries brian, we are not talkin about OJ core sources here. > I wont

Re: [JPP-Devel] DataSource URI_KEY vs FILE

On 05.10.2016 09:05, Michaël Michaud wrote: > Hi Ede, > > I made a quick fix to solve #431 but I wonder if it should'nt be fixed more > deeply. > > The bug has been introduced with the addition of DataSource.URI_KEY. > > It seems that for file based sources, we now have to keys to define the

<    5   6   7   8   9   10   11   12   13   14   >