On Wed, 7 Oct 2009, Ray Foulkes wrote:
writing that comment. The reality is that I am far from capable of
contributing code to JOSM at the moment. I intend to learn more and do
bits of coding on my own to see if I can understand better how JOSM is
structured and coded. Should I be so lucky
Jiri Klement wrote:
I've fixed #2480 by replacing LinkedList with ConcurrentLinkedQueue
(or at least I hope so, I don't have gps device with me to test it).
OK, I admit, I cannot locate the changed livegps. Can somebody point
me to where it is please.
Jiri, OOPs, sorry about misunderstanding the fix, it just shows how
little I know about JOSM. I thought that the problem was length
accessing the ArrayListwaypoint declared in the constructor of
LiveGpsLayer.
Please ignore my comment regarding any work that I might do - it is not
a good way of
I've fixed #2480 by replacing LinkedList with ConcurrentLinkedQueue
(or at least I hope so, I don't have gps device with me to test it).
Just a few thoughs about threading issues...
Making data structures thread safe does not necessary mean big
synchronization overhead. For example
Henrik Niehaus wrote:
Ray Foulkes schrieb:
Hi Jan, thankyou, I do not know what I was doing wrong the first time
around. I did as you suggested and created a java project using the
sources in core - it all worked and runs the main program OK. I can
navigate the Java e.g. find declarations,
On Sat, 3 Oct 2009, Ray Foulkes wrote:
Thanks Henrik, those videos look very comprehensive. I will patiently
follow them. Unfortunately I have to stop working today because I am to
travel from France to Glasgow by car(hopefully with
JOSM+livegps+surveyor on my eeepc running Ubuntu netbook
Dirk Stöcker wrote:
On Sat, 3 Oct 2009, Ray Foulkes wrote:
...etc.
The reason is easy - Make the data access thread safe. I think there are
sync keywords in Java to do so, but I do not really understand Java
multithreading completely (I'm more a C/C++ guy :-)
Hi Dirk, thanks for
On Sat, 3 Oct 2009, Ray Foulkes wrote:
In summary, I am nervous about simply putting in a patch to stop this
exception being raised. It would certainly solve my immediate problem
using JOSM+livegps+surveyor, but I don't think that it would be doing
the JOSM project a great favour for the
Hi Jan, thankyou, I do not know what I was doing wrong the first time
around. I did as you suggested and created a java project using the
sources in core - it all worked and runs the main program OK. I can
navigate the Java e.g. find declarations, references and run the main
application. etc.
Hi,
JOSM and most plug-ins already have prepared Eclipse projects. It
should be enough to import JOSM project and plug-ins you want to
debug. (File - Import - Project, disable copy to workspace)
If you want to be able to debug plug-in you must run plug-in project
but use JOSM main class as a
Ray Foulkes schrieb:
Hi Jan, thankyou, I do not know what I was doing wrong the first time
around. I did as you suggested and created a java project using the
sources in core - it all worked and runs the main program OK. I can
navigate the Java e.g. find declarations, references and run the
Ray Foulkes schrieb:
If I use an svn client to download to a directory then point Eclipse to
construct a java project itself, there are hundreds of Java errors which
I have not fully investigated but look nasty. Not surprising since the
build scripts I don't think are being used in that case.
12 matches
Mail list logo
