Hi,
If I can read the changeset there are lots of whitespace changes like
- private String wfsUrl;
+ private String wfsUrl;
Do we have guidelines for coding style? GDAL has this
https://trac.osgeo.org/gdal/wiki/rfc8_devguide
-Jukka Rahkonen-
-Alkuperäinen viesti-
Lähettäjä: ju
i seem to remember that a long time ago we agreed on
spaces only, no tabs
2 spaces indention
at least it is what i am using, when formatting java code.. ede
On 25.04.2016 09:06, Rahkonen Jukka (MML) wrote:
> Hi,
>
> If I can read the changeset there are lots of whitespace changes like
> - pri
Revision: 4903
http://sourceforge.net/p/jump-pilot/code/4903
Author: edso
Date: 2016-04-25 10:56:41 + (Mon, 25 Apr 2016)
Log Message:
---
featreq 422: wfs layer, add SRIDStyle using loading crs's epsg id
Modified Paths:
--
core/trunk/ChangeLog
core/t
Revision: 4904
http://sourceforge.net/p/jump-pilot/code/4904
Author: edso
Date: 2016-04-25 11:10:01 + (Mon, 25 Apr 2016)
Log Message:
---
revert Peppe's white space changes, but keeping previous SRID handling
Modified Paths:
--
core/trunk/src/de/latlon/d
Hey guys,
did just read this interesting post by Tim Sutton who is heading the
QGIS steering committee. Fortunately there isn't anything that the OJ
Dev team has to think about yet... the only exception may be the naming
of extensions. For instance I called on of my extensions OpenJUMP
HoRAE..
Hi Stefan,
interesting post. Thanks for the link.
There would be more things worth to discuss, in our little community.
I may be wrong but, regarding forks, I can see that, in the case of
Jump/OpenJump, it was the presence of divergent forks that helps OJ to go
on. I am thinking about both simple
Hi Michael,
I gave a look into your library cts 1.3.2 and found that there are parsers
for prj/proj codes. How do they work? Is there a method that gives back an
epsg code from prj string, like in geotools?
thanks
Peppe
--
