A final note,
GRASS functionality for raster processing may be best added to Sextante
[1]. A java toolbox that is used by OpenJUMP (and gvSIG and Kosmo) for
raster processing. Vector analysis functions could be added directly.
not sure how difficult it would be to port GRASS functions.
The past months I have put structures in place (main classes copied from
Sextante) to allow OpenJUMP to have its own Raster Analysis functions
without using Sextante.
stefan
[1] www.sextantegis.com
Landon Blake wrote:
Fahad:
I apologize for misspelling your name in the previous post. I also forgot the
link to the developer mailing list for OpenJUMP:
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Landon
Office Phone Number: (209) 946-0268
Cell Phone Number: (209) 992-0658
-----Original Message-----
From: discuss-boun...@lists.osgeo.org [mailto:discuss-boun...@lists.osgeo.org]
On Behalf Of Landon Blake
Sent: Wednesday, August 04, 2010 7:16 AM
To: OSGeo Discussions
Subject: RE: [OSGeo-Discuss] GRASS vs OpenJump
Faheed:
I'm involved in the development of OpenJUMP and will try to answer a couple of
your questions.
Faheed wrote: "I also want to know why OpenJump was not accepted by osgeo."
There isn't any blame to place on OSGeo. There are a couple of reasons why
OpenJUMP isn't an OSGeo project, but the main reason is a lack of resources to
get through the incubation process. There are currently about 4 people involved
with programming/administering OpenJUMP in a semi-regular basis. Our project
administrator (Stefan) is a very busy professor, our best programmer (Larry)
works for a busy company, our second best programmer (Michael) has moved onto
other projects and only helps out because he has mercy on our poor souls, and I
just work on OpenJUMP as a hobby.
So there is no one working on OpenJUMP full time. I suspect I'm as involved as
anyone, and I'd say I only rack about 8 to 16 hours a month. About ½ of that is
slinging code, the other ½ is responding to questions on our mailing lists.
It's hard to justify getting through the hoops for OSGeo incubation when you
can barely keep up with the bug reports. It's something we've discussed as an
OpenJUMP community several times, but everytime we conclude we lack the
resources to make the migration successfully.
If you are really interested in porting GRASS functionality to OpenJUMP, you
should subscribe to our developer's mailing list:
I will respond to any specific questions about OpenJUMP programming there. Of
course, there are lots of ways to help, not just porting GRASS functionality.
We need to test OpenJUMP on the LiveDVD, and write the OpenJUMP LiveDVD
documentation. There are also lots of little bugs to squish.
Of course, if you have a strong interest in seeing OpenJUMP become an OSGeo
project, and can but some effort into that, we could reconsider our earlier
decision to not start the incubation process.
Landon
Office Phone Number: (209) 946-0268
Cell Phone Number: (209) 992-0658
________________________________________
From: discuss-boun...@lists.osgeo.org [mailto:discuss-boun...@lists.osgeo.org]
On Behalf Of Fahad Rasheed
Sent: Wednesday, August 04, 2010 2:56 AM
To: discuss@lists.osgeo.org
Cc: grass-u...@lists.osgeo.org; grass-...@lists.osgeo.org;
grass-wind...@lists.osgeo.org
Subject: [OSGeo-Discuss] GRASS vs OpenJump
Hi all ,
I recently viewed OpenJump application written in JAVA which is also a GIS software but have less features when compared to GRASS GIS. What my plan is to contribute modules of GRASS GIS written in C/Python to OpenJump written in Java. Does osgeo or any grass developers have any objection in copying the code (mean the idea of making modules) to other OpenSource software like OpenJump. I do not mean of copying the whole code as same to java. What is my part of contribution is porting C/C++/Python code to Java and making some hacks on source code.
I also want to know why OpenJump was not accepted by osgeo.
Any sugeestion and comments are really welcomed..
Warning:
Information provided via electronic media is not guaranteed against defects
including translation and transmission errors. If the reader is not the
intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If you
have received this information in error, please notify the sender immediately.
_______________________________________________
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss
_______________________________________________
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss
_______________________________________________
Discuss mailing list
Discuss@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss