>>
>>
>>
>> I have tested the tools when I translated Kosmo into Finnish and I think
>> that they are useful and for most tools we do not have a counterpart.
>>
>>
>>
>> -Jukka Rahkonen-
>>
>>
>>
>> Giuseppe Aruta wrote
t.
-Jukka Rahkonen-
Giuseppe Aruta wrote:
[JPP-Devel] Kosmo CAD plugin for OpenJUMP
Greetings to all
I am working to port CAD toos from Kosmo SAIG (*) to OpenJUMP.
This toolbar has different tools, some that have a
similarcounterpart in OJ (like rotation ones) and
have tested the tools when I translated Kosmo into Finnish and I think
> that they are useful and for most tools we do not have a counterpart.
>
>
>
> -Jukka Rahkonen-
>
>
>
> Giuseppe Aruta wrote:
> [JPP-Devel] Kosmo CAD plugin for OpenJUMP
>
>
>
> Gre
+1 for both 1) and 2).
I have tested the tools when I translated Kosmo into Finnish and I think that
they are useful and for most tools we do not have a counterpart.
-Jukka Rahkonen-
Giuseppe Aruta wrote:
[JPP-Devel] Kosmo CAD plugin for OpenJUMP
Greetings to all
I am working to port CAD toos
Greetings to all
I am working to port CAD toos from Kosmo SAIG (*) to OpenJUMP.
This toolbar has different tools, some that have a similar counterpart in
OJ (like rotation ones) and other new that will increase OJ editing
capabilities, like drawing mirror, perpendicular lines or lines by COGO
comma
me, me, me,
my bad, shouldn't have been committed at all, fixed now.. ede
On 17.12.2014 08:32, Michael Michaud wrote:
> Hi,
>
> Can someone clarify the status of kosmo.propeties file in the project.
> The main file seems redundant with openjump language file,
> and the proxy setting specific s
Hi,
Can someone clarify the status of kosmo.propeties file in the project.
The main file seems redundant with openjump language file,
and the proxy setting specific stuff, translated in "es" and "it" is both
in kosmo and jump language files.
Michaël
-
develop and use
Aihe: [JPP-Devel] Kosmo SAIG
where can i find Kosmo SAIG sources. can anyone please give me the theory
and principles behind georeferencing to make a georeferencer
--
This SF.net email is sponsored by
and well you can georeference more or less vector data in openjump.
Functions are in Tools>Warp>... But Vector and Raser needs different
approaches to perform the referencing. E.g. rasters need to be
interpolated. Such interpolation functions are part of the Sextante
raster classes (I think the
Kosmo:
http://www.saig.es/index.php?lang=en
for Georeferencing I would ask you to look into standard GIS and remote
sensing text books.
However, have a look here:
http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?TopicName=Georeferencing_a_raster_dataset
http://www.columbia.edu/cu/lweb/indiv/d
where can i find Kosmo SAIG sources. can anyone please give me the theory
and principles behind georeferencing to make a georeferencer
--
This SF.net email is sponsored by
Make an app they can't live without
Enter the Bla
Giuseppe Aruta a écrit :
> Of coarse I invite (if they want to partecipate to this discussion)
> Michael Michaud and Larry Baker to say their opinion since they worked
> a lot on Beanshell and Jython consolles
Hi Giuseppe, and thanks to your efforts to improve collaboration.
Sharing beanshell
Sergio,
You wrote: "The plugin model that Kosmo uses is basically the same: we
have added
some methods to the interfaces and the abstract classes, but they
haven't been changed heavily. There is no plugín dependency system
implemented. The extension model have been also improved, but is almost
the
Of coarse I invite (if they want to partecipate to this discussion) Michael
Michaud and Larry Baker to say their opinion since they worked a lot on
Beanshell and Jython consolles
peppe
Giuseppe Aruta <[EMAIL PROTECTED]> ha scritto:
Hi.
1) Kosmo plugin model vs OpenJUMP
We ca
Hi.
1) Kosmo plugin model vs OpenJUMP
We can also consider other two ways to share tools between OpenJUMP and
Kosmo. Please correct me if I am wrong as I am not a developer
a) OpenJUMP introduced the Beanshell Consolle which, I think, it is still
under estimate between the users. Ne
Hi to all.
I'll shed a little bit light on the issues from a developer point of
view (both proposals from Giuseppe and another one that Sunburned
Surveyor mentioned):
1) Kosmo plug-in model
I'll start with a little bit of history to clarify some ideas:
Kosmo started on August 2005. Our starti
Hi Antonio,
let me resume the two i(my) proposal that could be object of this
discussion:. Just in order that developers can have an idea (from user point of
view).
1) a "save as" to project file format shared by two software. This format
(Jump, Kosmo or other) would not be alterate by s
Hi Landon, Peppe and everybody.
You are right Peppe, we were in East Holidays and I too needed to talk
with our main developer team people (really I am not a developer and I
am not able to speak about code, so I need them) :-) .
I hope this afternoon some information to continue speaking.
Bes
Hi London,
I think that the break of comunication in these days regarding Kosmo-OpenJUMP
common project was due to East holidays. And also because Antonio Muñoz
probabily needs to talk with other Saig team before taking a decision. Let us
wait a couple of days.
BTW Kosmo put on their web sit
Peppe,
Can you get a hold of the Kosmo team and see if there is any interest
in working on a common project file format?
The Sunburned Surveyor
On Thu, Mar 20, 2008 at 1:37 AM, Andreas Schmitz <[EMAIL PROTECTED]> wrote:
> Giuseppe Aruta wrote:
>
> Hi,
>
> > I saw on "List of changes" that Andrea
Giuseppe Aruta wrote:
Hi,
> 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).
yes, the SLD import/export is more or less finished. Unfortunately, I'll be
Peppe,
What you are talking about is possible, but I'm not sure it is simple.
:] We would need to only read and write the sections of the project
file that we are concerned with, and leave the other sections
untouched.
It could be done.
Let's see what the Kosmo guys have to say.
Landon
On Wed,
SS wrote:
> I didn't think about having
> the ability to
> export a Kosmo or OpenJUMP project file from each
> respective program,
> but it is a good idea.
or find a new 3rd file format that save both
projects characteristics (topologic rules, SLD, layer
and tables relations, hiperlinks
Peppe wrote: "Hi, the discussion is going down, probabily we need
more time to "digest" the proposal."
I don't think we need more time to digest. We just get busy and things
die off. Thanks to Peppe for keeping the conversation alive!
Kosmo Programmer wrote: "About plug-in models, both Openjump
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 d
Dear all.
Sorry for delay.
We think the way Giuseppe show and SS comment can be good like a medium
term.
This is because it is user driven, and the user could get the benefits.
About plug-in models, both Openjump and Kosmo are quite different, and
it is not easy to do it without a very hard jo
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 S
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 th
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
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
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 deve
I must agree with many of the points made by Stefan and Michael. I
know the language would be a barrier for me. :]
I think someone (I can't remember who) looked at this issue rather
closely and decided that it would be a huge amount of work to
integrate the Kosmo changes into OpenJUMP.
Having sai
Hi,
Kosmo benefits an important developper team, and I would have liked a
better cooperation between OpenJUMP and Kosmo.
I think the main problem is that kosmo started its development from an
old version of Jump, and when the first opensource version of kosmo was
published, jump and openjump ha
Hei Peppe,
the problem is simply that KOSMOs development is driven by project needs
and that they focus on a spannish user community.
On the one hand, there is the advantage if massive improvements and man
power by Kosmo. On the other I am not sure if this would be a good idea
if we allow a pr
Hi all
I recently started to collaborate with the Kosmo SAIG project, translating
the software in Italian.
I use both software with my geological project.I belive that the 2 software
together have a strong potentiality. I would like to find a common area for
the development of both "brot
Kosmo Team:
In three words: Absolutely brilliant job!
Congratulations.
Best regards,
Pedro Doria Meunier
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get th
I just visted the English page for Kosmo that was posted on the JUMP
users mailing list.
The page contains the following statements:
"Kosmo 0.8 contains most of the functions we would like to include in
Kosmo 1.0. We are very interested in the community's opinions and that
is why we are making th
37 matches
Mail list logo
