Hi again.

Your message arrived me later than my previous one, so I am here again.

Of course, the SLD is too a good way to give users benefit from both 
projects just in the moment OpenJump get it (it seems it is coming soon 
:-) ).

Best Regards
Antonio Muñoz

Giuseppe Aruta escribió:
> Hi, the discussion is going down, probabily we need
> more time to "digest"  the proposal.
> Anyhow I propone another "path" of collaboration
> betwee OJ and Kosmo.
> I saw on "List of changes" that Andreas is working a
> lot on SLD import/export plugin (I image ter related
> plugin (ImportSLDPlugIn.java and SLDImporter.java) are
> for  import/export SLD).
> On the other hand Kosmo can export simbology on SLD
> format.
> We could image to coordinate the projects so both
> software can read/save the same file... and use this
> SLD to exchange style (at least basics polygon color,
> line width, etc) between single shp layers (not only
> on the web).
> This probabily would be the minimun way that Kosmo
> adìnd OJ talk each other
>
> What do you think about?
>
> Peppe
>
> @Stefan: thanks for your "gift" for me on the the main
> OJ page! I relly appreciate, but I am quite shy to
> leave it a long time! :-)
>
>
> --- Sunburned Surveyor <[EMAIL PROTECTED]>
> ha scritto:
>
>   
>> Peppe has identified two (2) good opportunities for
>> collaboration,
>> aside from the aspect of library design that I
>> mentioned earlier.
>>
>> [1] Common file formats.
>> [2] Common plug-in model.
>>
>> These were excellent ideas by Peppe. (I would point
>> out that if Kosmo
>> and OpenJUMP can share file formats, for things like
>> projects, as an
>> example, then we can also share libraries for the
>> maniplation of these
>> file formats at a lower level.)
>>
>> Here is a question for Kosmo. How is their project
>> format file
>> different from the one currently used in OpenJUMP?
>> How have they
>> changed the plug-in framework?
>>
>> Having the answers to those questions would put us
>> on a path to some
>> real discussion about how to preserve compatibility
>> and cooperation in
>> at least these to areas.
>>
>> Good work Peppe?
>>
>> Any comments?
>>
>> The Sunburned Surveyor
>>
>> On Mon, Mar 17, 2008 at 11:55 AM, Giuseppe Aruta
>> <[EMAIL PROTECTED]> wrote:
>>     
>>> Dear  all,
>>>
>>> while waiting other opinions, I want to give "my 2
>>> cents" to this discussion.
>>>
>>> I think there is no need to derfine a "long" term
>>> project with the integration of tools from one
>>> softwere to the other.
>>>
>>> If I see the story of Jump and its "sons" and
>>>       
>> plugins,
>>     
>>> I image that the main problem is that Jump
>>>       
>> software
>>     
>>> suffered  loosing of compatibility with the former
>>> versions, expecially plugin.
>>>
>>> This happend with Kosmo and OJ, but this is
>>>       
>> happening
>>     
>>> with OJ 1.2 NB if we considerer that, with the new
>>> improvements, many plugin do not work (expecially
>>> Pirol's ones which represent one of the most
>>> specialized OJ "battlefront").
>>>
>>> I image that a "short" term common project between
>>> Kosmo and OpenJUMP would be to work on a common
>>>       
>> way to
>>     
>>> open/save projects. If Kosmo could open OJ project
>>>       
>> and
>>     
>>> "viceversa"  it will give a great benefits for the
>>> user who can switch between the two software and
>>>       
>> use
>>     
>>> what they need.  This probabily won't effect on
>>>       
>> any
>>     
>>> other prblem (comatibility/client driven/etc)
>>>
>>> Is it practicable?
>>>
>>> Regards
>>>
>>> Peppe
>>>
>>>
>>>
>>>       
>>>> Dear Antonio,
>>>>
>>>> I thank you for your comments. It is always good
>>>>         
>> to
>>     
>>>> know your (positive)
>>>> perspective on such a colaboration.
>>>>
>>>> stefan
>>>>
>>>> listas schrieb:
>>>>         
>>>>> Hi all.
>>>>>
>>>>> First time, many thanks to Peppe, not only for
>>>>>           
>>>> your nice collaboration
>>>>         
>>>>> with Kosmo, but for your interest in find "a
>>>>>           
>>>> common area for the
>>>>         
>>>>> development of both brother" (I really like
>>>>>           
>> that
>>     
>>>> definition).
>>>>         
>>>>> I would like to share some ideas/feeling about
>>>>>           
>>>> your comments.
>>>>         
>>>>> As you said, Kosmo is developed by project
>>>>>           
>> needs,
>>     
>>>> but maybe it is better
>>>>         
>>>>> to explain a little more the meaningful (our
>>>>>           
>>>> meaningful) of "project
>>>>         
>>>>> needs and project driven development":
>>>>>
>>>>> Our main objective is not to develop Kosmo
>>>>>           
>> itself.
>>     
>>>>  Our main objetives
>>>>         
>>>>> are the "client driven projects".  To be able
>>>>>           
>> of
>>     
>>>> realize correctly those
>>>>         
>>>>> projects, we need continuously build and
>>>>>           
>> improve
>>     
>>>> Kosmo.  So, about a
>>>>         
>>>>> "strict schedule" (a good subject to analyze),
>>>>>           
>>>> this exist, but mainly
>>>>         
>>>>> for those projects.  So, strict schedule for
>>>>>           
>> Kosmo
>>     
>>>> exist only for what
>>>>         
>>>>> is neccesary to carry out our commitment with
>>>>>           
>>>> clients.  Without clients
>>>>         
>>>>> we could not maintain Kosmo project.  We are
>>>>>           
>> just
>>     
>>>> a small company who
>>>>         
>>>>> think we are able to work and live in a free
>>>>>           
>>>> software model, and return
>>>>         
>>>>> to community all we can.
>>>>>
>>>>> About community, Kosmo is not only focused on
>>>>>           
>> a
>>     
>>>> spanish user community.
>>>>         
>>>>> In fact, in the last 1.2  versión it has been
>>>>>           
>>>> translated into italian
>>>>         
>>>>> (thanks to Peppe), russian (thanks to Sergey
>>>>>           
>>>> Smirnov), german (thanks to
>>>>         
>>>>> Johannes Sommer),  brasilian portuguese
>>>>>           
>> (thanks to
>>     
>>>> Territoriolivre.net
>>>>         
>>>>> people), baske (thanks to baske administration
>>>>>           
>>>> people). Some other new
>>>>         
>>>>> languajes are coming soon (czech, slovak...)..
>>>>>           
>>  We
>>     
>>>> directly maintain
>>>>         
>>>>> both, english and spanish version.
>>>>>
>>>>> As you said, we have an important developmet
>>>>>           
>> team,
>>     
>>>> because we have
>>>>         
>>>>> client driven projects that let us to maintain
>>>>>           
>> it.
>>     
>>>>  We think other way
>>>>         
>>>>> it is not possible for us to improve and to
>>>>>           
>> let
>>     
>>>> Kosmo growing.
>>>>         
>>>>> We have translated/included a lot of
>>>>>           
>> code/tools
>>     
>>>> from
>>>>         
>>>>> OpenJUMP/Jump/DeeJump/Pirol/Sigle projects
>>>>>           
>> (and
>>     
>>>> other no Jump family
>>>>         
>>>>> utilities).
>>>>>
>>>>> Like some of you we would have liked a better
>>>>>           
>>>> cooperation.  We still
>>>>         
>>>>> would like it.
>>>>>
>>>>> -Maybe all we (you and us) have been, and will
>>>>>           
>>>> continue very busy to do
>>>>         
>>>>> enough work in draw a common way to work
>>>>>           
>> together.
>>     
>>>>> -Maybe it is not very easy.
>>>>> -Maybe we too could do an additional effort
>>>>>           
>> and
>>     
>>>> collaborate in help
>>>>         
>>>>> translate and merge OpenJUMP into Kosmo.
>>>>> -Maybe would be neccesary strict schedule only
>>>>>           
>> for
>>     
>>>> those who need to
>>>>         
>>>>> attend different/external Kosmo project
>>>>>           
>> commitment
>>     
>>>> (private commitment),
>>>>         
>>>>> and absolutely free to dedicate the time they
>>>>>           
>>>> want, when they want for
>>>>         
>>>>> people developing Kosmo itself.  In other
>>>>>           
>> words,
>>     
>>>> none strict schedule
>>>>         
>>>>> for Kosmo itself.
>>>>>
>>>>> About Intevation/LatLon and SkyJUMP team, we
>>>>>           
>> think
>>     
>>>> it would be a very
>>>>         
>>>>> good opportunity to get a positive synergy
>>>>>           
>> between
>>     
>>>> us.
>>>>         
>>>>> We are not sure how easy/difficult arrive to
>>>>>           
>> this
>>
>>     
> === message truncated ===
>
>
>
>       Inviato da Yahoo! Mail. 
> Tanti modi per restare in contatto con chi vuoi.
> http://it.docs.yahoo.com/mail/overview/index.html
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
>   

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to