Hi,
I don't see why this needs so much discussion. Everything has been said a
good while ago in this thread. Now it seems to become more and more a
discussion about taste. And as we all know taste is diffrent.
It is good to know that there are two approaches right now. JOSM-ng for
the guys liking
Hi,
I did some investigation on how to build the .app on the fly and
discovered the following solution using ANT:
2 libs are needed:
* JarBundler: http://informagen.com/JarBundler/
* Xerces: http://xerces.apache.org/xerces2-j/
JarBundler uses Xerces (the xercesImpl.jar to be precise).
An ANT b
> I have created a .app for JOSM too. I increased the memory for it to
> work. It needed to be done in a special way, through the Java VM
> properties rather than the memory setting in the .plist.
hm... yes, of course. You tell the Java VM how many memory to use. The
.plist just holds the informa
Hi,
>> I occasionally use a Mac as well. I have the .jar lying around on the
>> desktop, and double-click it to start JOSM. What advantage does
>> a .app have over this?
>
> One drawback of starting it like that is that you don't get to boost
> the memory available to JOSM, something I've found I
Hi,
I'm using a Mac together with JOSM for tracking. I don't like the way I
have to start JOSM. So I made a .app (using "Jar Bundler" and
"IconComposer") from the latest JOSM build.
I don't want to break the line by simply publishing it somewhere. So my
question is: What can I do? Is there a plac