Hei Guys,

thank you for your posts/comments and especially Michael for the indept 
analysis of Kosmo!
So the decision is quite clear: we leave it as it is and will watch if 
Kosmo receives a mature stage.

now to different things:

- I have added a Reverse Line Direction tool to Geometry function..

- @Larry:  I was looking for the autocomplete polygon function in 
SkyJUMP but could not find. How does it work?

yours,
stefan

Ugo Taddei schrieb:
> Hi R1,
> 
> erwan bocher wrote:
>> Hi all,
>>
>> I send to u a copy of my answer because I have a problem with the JPP 
>> List.I receive but I can not send.
>>
>> Cheers
>>
>> R1.
>>
>>
>> ---------- Forwarded message ----------
>> From: *erwan bocher* <[EMAIL PROTECTED] 
>> <mailto:[EMAIL PROTECTED]>>
>> Date: Mar 3, 2007 9:50 AM
>> Subject: Re: [JPP-Devel] Suggestion by Pedro on changing to Kosmo
>> To: "List for discussion of JPP development and use." 
>> <jump-pilot-devel@lists.sourceforge.net 
>> <mailto:jump-pilot-devel@lists.sourceforge.net>>
>>
>> Hi all,
>>
>> Concerning ,SIGLE and my laboratory opinion's. Kosmo has made many 
>> improvements on the JUMP. It is a good work. Nevertheless, I think 
>> that we shouldn't use the code of Kosmo but rather methodology. There 
>> is many dependencies with other projects. For examples :
>>
>> - to load dxf files Kosmo uses the work made by the gvSIG friends
>> - to load raster layers, Kosmo uses also a great gvSIG development 
>> (JGDAL)
> 
> Agree. I also think that having dependencies to native libs is very bad.
> 
>>
>> And in the lib jar folder,  we can see andami, Fmap, GDBMS 0.8.. . . 
>> the bases libraries for the gvSIG GIS (60 jar files).
> 
> In other words, a mess.
> 
>>
>> As said Landon, one of the best things about OpenJUMP is its stability 
>> and I add "the size".
>> OpenJUMP offers many functionalities with very few libraries dependences.
>>
>> I agree with Larry and Landon :
>> 1. " I would recommend putting off any decision
>> until there is a mature version of Kosmo."
> 
> Agree.
> 
>>
>> 2. "OpenJUMP was our idea for a common platform or brand that these 
>> different "brands" could use. I don't think I ever imagined building 
>> an OpenJUMP that would fit everyone's specialized needs. I instead 
>> imagined that the different brands would sharea as much code as 
>> possible in the common "core" that would be OpenJUMP."
> 
> To the point, that is précisément ;-)
> 
> Au revoir,
> 
> Ugo
> 
> 
>>
>>
>> Cheers.
>>
>> R1.
>>
>>
>> --------------------
>> Ingénieur de recherche
>> Docteur en géographie,
>> spécialité géomatique
>> École Centrale de Nantes
>> Institut de recherche en sciences et techniques de la ville
>> http://www.irstv.cnrs.fr/
>> http://geosysin.iict.ch/irstv-trac/wiki 
>> <http://geosysin.iict.ch/irstv-trac/wiki>
>> http://r1.bocher.free.fr <http://r1.bocher.free.fr/>
>> http://www.projet-sigle.org <http://www.projet-sigle.org/>
>>
>>
>>
>>
>>
>> On 3/3/07, *Sunburned Surveyor* < [EMAIL PROTECTED] 
>> <mailto:[EMAIL PROTECTED]>> wrote:
>>
>>     I haven't had a chance to test drive Kosmo like Larry has, so I
>>     can't give an objective comments on this idea of "jumping" to
>>     Kosmo's core. However, I would like to offer some quick thougts, and
>>     add to some of the things Larry and Stefan mentioned.
>>          I think we need to remember that one of the best things about
>>     OpenJUMP is its stability. I don't deny that there seem to be great
>>     things going on with Kosmo. I was reading over there previous
>>     message about some of the changes they had made, and I must admit I
>>     was nearly overwhelmed by all they had done. I think they will
>>     continue to make rapid progress with a staff of 9 devoted
>>     developers. I don't think there is any way Stefan and  I, or even
>>     Vivid Solutions, has the ability to throw that many bodies at
>>     OpenJUMP improvements.
>>          However, after recognizing the rapid progress Kosmo will 
>> experience,
>>     we need to acknowlege some important realities identified in Larry's
>>     comments. It sounds like development of Kosmo is driven by some very
>>     specific client/customer requests, and that the organization behind
>>     Kosmo's development have some very specific ideas of what they would
>>     like to accomplish.This is an ideal environment to bring about the
>>     rapid improvements they are planning. They will be focused and won't
>>     have the burdens that come with a more open community-based
>>     development process.
>>          The orignial purpose of the JPP was to encourage 
>> "collaborative" or
>>     "cooperative" development of  the different JUMP "brands". OpenJUMP
>>     was our idea for a common platform or brand that these different
>>     "brands" could use. I don't think I ever imagined building an
>>     OpenJUMP that would fit everyone's specialized needs. I instead
>>     imagined that the different brands would sharea as much code as
>>     possible in the common "core" that would be OpenJUMP. I think we can
>>     still accomplish this "vision" for OpenJUMP and the JPP by
>>     judicously choosing the things we would like to integrate from
>>     Kosmo. They can in turn judicously choose what they would like to
>>     "take" from us.
>>          Think of OpenJUMP as the Linux Kernel, and Kosmo as a 
>> distribution
>>     of Linux like Debian or Red Hat. We want to keep a kernel that can
>>     be used by a lot of different "distros".
>>          I need to speak some more about these issues. I hope I can 
>> find time
>>     later this weekend.
>>          The Sunburned Surveyor
>>     On 3/2/07, *Larry Becker* <[EMAIL PROTECTED]
>>     <mailto:[EMAIL PROTECTED]>> wrote:
>>
>>         Hi Stefan,
>>
>>         >  > Putting all together it's quite tempting to say: "...why
>>         don't we simply
>>         >  > adopt the Core from Kosmo as the OJ Core altogether...?!?".
>>         >  >
>>         >  What is your oppinon on that? Pro's & Con's?
>>         >  (this goes especially to Larry, SIGLE/Erwan, Ugo, Michael and
>>         the Pirol
>>
>>         When you check out Kosmo rc1, I think you'll find that it has 
>> made
>>         many changes to the basic JUMP interface.  Some are 
>> understandable,
>>         but others seem to be just gratuitous. From the SkyJUMP
>>         perspective,
>>         (small maps, easy to use, many CAD-like editing tools) there 
>> doesn't
>>         seem to be much to take away.  Others will no doubt be excited
>>         by the
>>         heavy weight data sources, and removal of memory bound
>>         restrictions.
>>         I'm still going through it, but it looks to still be a work in
>>         progress compared to OJ.  I would recommend putting off any 
>> decision
>>         until there is a mature version of Kosmo.
>>
>>         regards,
>>         Larry Becker
>>
>>         
>> -------------------------------------------------------------------------
>>         Take Surveys. Earn Cash. Influence the Future of IT
>>         Join SourceForge.net's Techsay panel and you'll get the chance
>>         to share your
>>         opinions on IT & business topics through brief surveys-and 
>> earn cash
>>         
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>>         
>> <http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV> 
>>
>>         _______________________________________________
>>         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
>>
>>
>>
>>     
>> -------------------------------------------------------------------------
>>     Take Surveys. Earn Cash. Influence the Future of IT
>>     Join SourceForge.net's Techsay panel and you'll get the chance to
>>     share your
>>     opinions on IT & business topics through brief surveys-and earn cash
>>     
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>>     
>> <http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV> 
>>
>>     _______________________________________________
>>     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
>>     <https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel>
>>
>>
> 

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to