GIT --- http://github.com/migurski/paperwalking
Shaun
On 10 Nov 2009, at 15:02, Ævar Arnfjörð Bjarmason wrote:
Hi. I was going to hack JOSM so that it displays the description of
walking papers in info dialogs / tooltips / the layer selector.
Could you please add this to the span
On Tue, Nov 10, 2009 at 3:17 PM, Shaun McDonald o...@shaunmcdonald.me.uk
wrote:
GIT --- http://github.com/migurski/paperwalking
Cool. I've patched my fork here with this functionality:
http://github.com/avar/paperwalking
Sent a pull request to migurski/paperwalking.
On Tuesday 10 November 2009, Ævar Arnfjörð Bjarmason wrote:
Cool. I've patched my fork here with this functionality:
http://github.com/avar/paperwalking
Sent a pull request to migurski/paperwalking.
If only JOSM development were so flexible and easy.
/me runs and hides.
robert.
On Tue, 10 Nov 2009, Robert Scott wrote:
On Tuesday 10 November 2009, Ævar Arnfjörð Bjarmason wrote:
Cool. I've patched my fork here with this functionality:
http://github.com/avar/paperwalking
Sent a pull request to migurski/paperwalking.
If only JOSM development were so flexible and easy.
On Tue, 2009-11-10 at 17:54 +0100, Dirk Stöcker wrote:
P.S. When I last tried git I found it very frustrating to reach otherwise
very easy tasks. It may be optimal for distributed development, but makes
the normal development more complicated.
It has a very steep learning curve which I think
On Tuesday 10 November 2009, Dirk Stöcker wrote:
If only JOSM development were so flexible and easy.
/me runs and hides.
Aiming with my long range rifle ...
Do you wanna excuse? 10 .. 9 .. 8 ..
In all seriousness, it would make life a lot easier for those of us who submit
patches
I'm personally an advocate of Mercurial/bitbucket.org over git/github.org,
as I find it easier to use and understand. And Mercurial is supposed to
work better for windows users (I personally don't know).
I use Mercurial on several Windows platforms, and it works well and has
64-bit
This changeset:
http://josm.openstreetmap.de/changeset/2427/
removes the way_bbox_cache. Unfortunately, this just *KILLS*
performance. It makes some of my way search tests 10-20x slower. We
use getBBox() really, really often and the CPU we use repeatedly
recreating them ends up being
It's not possible to get it easily back as it was, but Way.getBBox()
should do the caching now. When I get time I'll add events to Dataset
so that Way will know when it's nodes were changed and update it's
bbox.
On Tue, Nov 10, 2009 at 6:33 PM, Dave Hansen d...@sr71.net wrote:
This changeset:
