Re: [JPP-Devel] ecw license WAS: Re: ecw bugfix
Hence, I think the implementation was done by Jon Aquino - as it came from JUMP 1.2 and thanks to Jukka for the license text info. After reading this, I think we could just distribute them (in the release) - but we need at least to add the license note from ER Mapper SDK 3. But that's a personal opinion. stefan -- Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] refactoring of addMainMenuItem
thanks for the clarifying Michael stefan On 15/09/2011 12:53 AM, Michaël Michaud wrote: > Hi Stefan, >> Hi Michael, >> >> can I asked why you do a refactoring of addMainMenuItem? > It started with a change from Matthias who noticed that addMainMenuItem > methods have accumulated over the time, some returning void, new ones > returning JMenuItem. > He tried to homogeneize the api making them all return JMenuItem which > is often helpful, but one week after, I realized that it has broken > plugin compatibility. > We tried to find another solution to clean the api without breaking > compatibility, and Ede suggested to add a new central method. All the > the old methods will use this new one so that compatibility is > preserved, and some old ones will be deprecated so that one day, we can > clean the class. > > As changing this class is quite unsafe, I have waited 1.4.2 release so > that we have time to check nothing has been broken before the next > release ;-) >> Will plugins be concerned? > I Tried not to break anything. > New plugins will have to stop using deprecated methods (you can see the > committed code in svn, as inline javadoc is not uptodate) > > Cheers, > > Michaël >> cheers from Calgary >> stefan >> >> >> -- >> Doing More with Less: The Next Generation Virtual Desktop >> What are the key obstacles that have prevented many mid-market businesses >> from deploying virtual desktops? How do next-generation virtual desktops >> provide companies an easier-to-deploy, easier-to-manage and more affordable >> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ >> ___ >> Jump-pilot-devel mailing list >> Jump-pilot-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >> >> > > -- > Doing More with Less: The Next Generation Virtual Desktop > What are the key obstacles that have prevented many mid-market businesses > from deploying virtual desktops? How do next-generation virtual desktops > provide companies an easier-to-deploy, easier-to-manage and more affordable > virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ > ___ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] ecw license WAS: Re: ecw bugfix
I can see that the imagery support appeared with the Jump 1.2 version by Vivid solutions from October 31 2006. It included already support for ECW and MrSID Installation guide says: 4.4 IMAGERY ADD-INS 4.4.1 ErMapper ErMapper users should download the ErMapper.jar file from http://www.ermapper.com/. The jar should be placed into the lib directory, and added to the classpath. 4.4.2 MrSID MrSID users should download the mrsidgeodecode.exe and mrsidgeoinfo.exe utilities from http://www.lizardtech.com/. The files should be placed in a local directory, and added to the system path. Note: you may add the exe files to the system path within the launch script. 4.4.3 Imagery Hardware Support Imagery user may also consider installing hardware support for JAI from http://java.sun.com/products/java-media/jai/. A software version is included with JUMP, you may need to remove the jai*.jar files from the classpath after installing the hardware support into your JVM. The guide does not mention .dll files but ECW images cannot be opened without them with JUMP 1.2. With dlls it works still very well. First time I can see ECW dlls appear with OpenJUMP on this computer is: D:\openjump-20070503-0016\lib\ext 21.10.2004 15:14 1 024 034 NCSEcw.dll -Jukka Rahkonen- Lähettäjä: edgar.sol...@web.de [edgar.sol...@web.de] Lähetetty: 15. syyskuuta 2011 16:30 Vastaanottaja: OpenJump develop and use Aihe: [JPP-Devel] ecw license WAS: Re: ecw bugfix ok, i now changed the topic accordingly. first off i guess we need to find the correct license. anybody knows who implemented native win32 ecw support? can we contact him to receive the original license that cam with that version of the sdk? On 15.09.2011 12:46, Rahkonen Jukka wrote: > Hi, > > I tried to get some understandment about how the license text for the ECW > SDK/ECW JPEG 2000 SDK/ERDAS ECW/JP2 SDK has changed but it is not easy. > However, it looks like there in no problem in using .dll files from the > independent ER Mapper time before Leica Geosystems bought the company in > 2007. All the old programs I checked (Irfan View, ArcView, ArcGIS 9, MapInfo > Professional etc.) just have copied the NCS***.dll files from the > "redistributable" directory of the ECW SDK. I could not find a copy of ER > Mapper ECW licence from those programs but it is possible that it is included > somewhere on the help files. there should be a the necessary eula appendix as demanded by the two ecw EULAs i have seen so far. this would be the license that would have to add to our license collection as well. still wich is the correct complete licens for our binaries (ermapper.jar+NCS*.dlls). this one http://www.calculate-linux.org/packages/licenses/ECWPL ? could somebody supply me with the original sdk used? i would have a look at it and try to shed some more light on it as the ECWPL is obviously completely different to recent ecw sdk licenses. > EULA from November 2007 did not change much the situation with OpenJUMP I > think. What we use are exactly the files in the "redistributables" directory > > " 2. LICENSE GRANT > 2.1. Non-Commercial Use. > 2.1.1. Subject to all other terms of this Agreement, You are hereby granted a > royalty-free, nonexclusive, worldwide license to use the ECW/JP2 CODEC SDK to > create and distribute END APPLICATIONS that DECODE and/or ENCODE for > NON-COMMERCIAL USES. > 2.1.2. Subject to all other terms of this Agreement, You are hereby granted a > royalty-free, worldwide license to use the ECW/JP2 CODEC SDK to create and > distribute LIBRARIES. In distributing LIBRARIES, You are licensed only to > distribute those compiled portions of the ECW/JP2 CODEC SDK in the > "redistributables" directory, which contains binaries that another > application using the LIBRARY will link to." i am not sure if that license applies to our binaries > > The whole EULA text is citated in gdal develor thread > http://www.osgeo.org/pipermail/gdal-dev/2007-December/015248.html > > At that time the SDK version was 3.x.x. The current version is 4.2 and the > company name ERDAS. I do not think that OpenJUMP could even theoretically use > the new 4.x SDK. ERDAS is marketing the system for streaming ECW imagery > through the internet with ECWP protocol and new license terms mandate that > any software using the version 4.x ECW must be able to read both static .ecw > image files and content from servers sending ECWP streams. even the new 'cited license' above has a statement for mandatory stream support. so we would have to look if our binaries came from before or actually legally have to drop the support. > We could consider to deliver the old ECW .dll files bundled with OpenJUMP > like we do now. We cannot really deliver OJ without the dlls and give > instruction for the users to download dlls separately, because ERDAS does not > have version 3.x downloads. It was not allowed at the v. 3.x time to
[JPP-Devel] ecw license WAS: Re: ecw bugfix
ok, i now changed the topic accordingly. first off i guess we need to find the correct license. anybody knows who implemented native win32 ecw support? can we contact him to receive the original license that cam with that version of the sdk? On 15.09.2011 12:46, Rahkonen Jukka wrote: > Hi, > > I tried to get some understandment about how the license text for the ECW > SDK/ECW JPEG 2000 SDK/ERDAS ECW/JP2 SDK has changed but it is not easy. > However, it looks like there in no problem in using .dll files from the > independent ER Mapper time before Leica Geosystems bought the company in > 2007. All the old programs I checked (Irfan View, ArcView, ArcGIS 9, MapInfo > Professional etc.) just have copied the NCS***.dll files from the > "redistributable" directory of the ECW SDK. I could not find a copy of ER > Mapper ECW licence from those programs but it is possible that it is included > somewhere on the help files. there should be a the necessary eula appendix as demanded by the two ecw EULAs i have seen so far. this would be the license that would have to add to our license collection as well. still wich is the correct complete licens for our binaries (ermapper.jar+NCS*.dlls). this one http://www.calculate-linux.org/packages/licenses/ECWPL ? could somebody supply me with the original sdk used? i would have a look at it and try to shed some more light on it as the ECWPL is obviously completely different to recent ecw sdk licenses. > EULA from November 2007 did not change much the situation with OpenJUMP I > think. What we use are exactly the files in the "redistributables" directory > > " 2. LICENSE GRANT > 2.1. Non-Commercial Use. > 2.1.1. Subject to all other terms of this Agreement, You are hereby granted a > royalty-free, nonexclusive, worldwide license to use the ECW/JP2 CODEC SDK to > create and distribute END APPLICATIONS that DECODE and/or ENCODE for > NON-COMMERCIAL USES. > 2.1.2. Subject to all other terms of this Agreement, You are hereby granted a > royalty-free, worldwide license to use the ECW/JP2 CODEC SDK to create and > distribute LIBRARIES. In distributing LIBRARIES, You are licensed only to > distribute those compiled portions of the ECW/JP2 CODEC SDK in the > "redistributables" directory, which contains binaries that another > application using the LIBRARY will link to." i am not sure if that license applies to our binaries > > The whole EULA text is citated in gdal develor thread > http://www.osgeo.org/pipermail/gdal-dev/2007-December/015248.html > > At that time the SDK version was 3.x.x. The current version is 4.2 and the > company name ERDAS. I do not think that OpenJUMP could even theoretically use > the new 4.x SDK. ERDAS is marketing the system for streaming ECW imagery > through the internet with ECWP protocol and new license terms mandate that > any software using the version 4.x ECW must be able to read both static .ecw > image files and content from servers sending ECWP streams. even the new 'cited license' above has a statement for mandatory stream support. so we would have to look if our binaries came from before or actually legally have to drop the support. > We could consider to deliver the old ECW .dll files bundled with OpenJUMP > like we do now. We cannot really deliver OJ without the dlls and give > instruction for the users to download dlls separately, because ERDAS does not > have version 3.x downloads. It was not allowed at the v. 3.x time to deliver > dlls separately but they should be included with the main software. Therefore > I do not believe we could keep copies of the .dll files for download on OJ > web side. Alternative is to remove the ECW support totally. For me the > current situation with dll files included in the release version but not in > the nightly builds fine because I do have some ECW images and OpenJUMP is > handling them fine. actually there are three options here - offer a bundle to download and copy to /lib - include in distribution zip - drop the support we should clear the correct license for our binaries and decide accordingly. > > When it comes to 4.x version, perhaps it would be best to acquire the > possible ECW support through an external library like GDAL or Geotools of > Sextante instead of building a new native support into OpenJUMP. just checked geotools2 and they use a gdal binding to read ecw, http://www.gdal.org/frmt_ecw.html which in turn would need one of these http://trac.osgeo.org/gdal/wiki/DownloadingGdalBinaries i checked - win gisinternals.com dailies v1.8 which came with ecw libraries http://www.gisinternals.com/sdk/PackageList.aspx?file=release-1600-x64-gdal-1-8-mapserver-6-0.zip - linux ubuntugis build unstable also v1.8 something which had no ecw support out of the box http://trac.osgeo.org/ubuntugis/wiki/UbuntuGISRepository but that is just observation, no judgement here. my take would be to implement gt2 datasources finally and therefor play
Re: [JPP-Devel] ecw bugfix
On 15.09.2011 06:39, Rahkonen Jukka wrote:
> Hi,
>
> So the point was that the ECW license said "licensed under a license similar
> to a General Public
> License ("GPL") and at no charge to the public" but GPL allows anybody to
> start selling OpenJUMP.
>
> We may by right with the decision but we are alone. GvSIG, Kosmo and QGIS all
> seem to come witd ECW dlls.
No that is not right. It is an issue to people distributing openjump for money,
if they do, they have to care about it. We don't commercially distribute it so
we don't.
Still i assume this license is not the one for our current binaries.
..ede
> -Jukka Rahkonen-
>
> Stefan Steiniger wrote:
>
>> ok.. found something in our list history on the license.
>
>> http://www.mail-archive.com/jump-pilot-devel@lists.sourceforge.net/msg00616.html
>
>> Thats why we have also a "dummy class" for the nightly build
>
> stefan
>
> --
> Doing More with Less: The Next Generation Virtual Desktop
> What are the key obstacles that have prevented many mid-market businesses
> from deploying virtual desktops? How do next-generation virtual desktops
> provide companies an easier-to-deploy, easier-to-manage and more affordable
> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
> ___
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
> --
> Doing More with Less: The Next Generation Virtual Desktop
> What are the key obstacles that have prevented many mid-market businesses
> from deploying virtual desktops? How do next-generation virtual desktops
> provide companies an easier-to-deploy, easier-to-manage and more affordable
> virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
> ___
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
--
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops? How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] ecw bugfix
Hi,
I tried to get some understandment about how the license text for the ECW
SDK/ECW JPEG 2000 SDK/ERDAS ECW/JP2 SDK has changed but it is not easy.
However, it looks like there in no problem in using .dll files from the
independent ER Mapper time before Leica Geosystems bought the company in 2007.
All the old programs I checked (Irfan View, ArcView, ArcGIS 9, MapInfo
Professional etc.) just have copied the NCS***.dll files from the
"redistributable" directory of the ECW SDK. I could not find a copy of ER
Mapper ECW licence from those programs but it is possible that it is included
somewhere on the help files.
EULA from November 2007 did not change much the situation with OpenJUMP I
think. What we use are exactly the files in the "redistributables" directory
" 2. LICENSE GRANT
2.1. Non-Commercial Use.
2.1.1. Subject to all other terms of this Agreement, You are hereby granted a
royalty-free, nonexclusive, worldwide license to use the ECW/JP2 CODEC SDK to
create and distribute END APPLICATIONS that DECODE and/or ENCODE for
NON-COMMERCIAL USES.
2.1.2. Subject to all other terms of this Agreement, You are hereby granted a
royalty-free, worldwide license to use the ECW/JP2 CODEC SDK to create and
distribute LIBRARIES. In distributing LIBRARIES, You are licensed only to
distribute those compiled portions of the ECW/JP2 CODEC SDK in the
"redistributables" directory, which contains binaries that another application
using the LIBRARY will link to."
The whole EULA text is citated in gdal develor thread
http://www.osgeo.org/pipermail/gdal-dev/2007-December/015248.html
At that time the SDK version was 3.x.x. The current version is 4.2 and the
company name ERDAS. I do not think that OpenJUMP could even theoretically use
the new 4.x SDK. ERDAS is marketing the system for streaming ECW imagery
through the internet with ECWP protocol and new license terms mandate that any
software using the version 4.x ECW must be able to read both static .ecw image
files and content from servers sending ECWP streams.
We could consider to deliver the old ECW .dll files bundled with OpenJUMP like
we do now. We cannot really deliver OJ without the dlls and give instruction
for the users to download dlls separately, because ERDAS does not have version
3.x downloads. It was not allowed at the v. 3.x time to deliver dlls separately
but they should be included with the main software. Therefore I do not believe
we could keep copies of the .dll files for download on OJ web side.
Alternative is to remove the ECW support totally. For me the current situation
with dll files included in the release version but not in the nightly builds
fine because I do have some ECW images and OpenJUMP is handling them fine.
When it comes to 4.x version, perhaps it would be best to acquire the possible
ECW support through an external library like GDAL or Geotools of Sextante
instead of building a new native support into OpenJUMP.
-Jukka Rahkonen-
> -Alkuperäinen viesti-
> Lähettäjä: Michaël Michaud [mailto:michael.mich...@free.fr]
> Lähetetty: 15. syyskuuta 2011 9:37
> Vastaanottaja: OpenJump develop and use
> Aihe: Re: [JPP-Devel] ecw bugfix
>
> Hi,
>
> Licenses agreements are really a puzzle for me :-( .
>
> Thanks Stefan for finding this old exchange of mails.
>
> I don't understand clearly Oliver argument. Why the terms "and at no
> charge to the public" should be a concern? Do we charge
> OpenJUMP users?
> Do we need to remove dll or do we need to include its license in the
> distribution so that distributors who want to charge their users know
> they have to remove them first? (OK, currently we even do not
> do that in
> OJ license part)
>
> Another question is : do we have a link to these dll
> licenses. For 1.4.1
> distro, I Googled to find them but just found licenses about
> their new
> products. Would be interesting to know if license has changed
> and what
> is the license for these old dll. Maybe we should contact
> ermapper for that?
>
> Last question is : is there a difference between including dll in the
> distribution and giving a link to a repository of JPP
> project? I think
> that usage for restricted license if to give a link to the copyright
> owner site. Problem is that these dll are not distributed anymore by
> ermapper.
>
> Too bad, each time I look for a clear answer to a simple license
> question, I get three more questions and still no answer :-( .
>
> Michaël
>
>
> Le 15/09/2011 06:39, Rahkonen Jukka a écrit :
> > Hi,
> >
> > So the point was that the ECW license said "licensed under
> a license similar to a General Public
> > License ("GPL") and at no charge to the public" but GPL
> allows anybody to start selling OpenJUMP.
> >
> > We may by right with the decision but we are alone. GvSIG,
> Kosmo and QGIS all seem to come witd ECW dlls.
> >
> > -Jukka Rahkonen-
> >
> > Stefan Steiniger wrote:
> >
> >> ok.. found something in our list history o
