Re: [josm-dev] jttt and private class members

2009-07-28 Thread Jiri Klement
Another area is possibility to build spatial index - it should make map paint and functions like getNearestNode much faster. Spatial index and painting only primitives that are not too small is imho the main reason why is josmng so much faster than josm. Btw. Currently I'm not continuing on the re

Re: [josm-dev] jttt and private class members

2009-07-28 Thread Karl Guggisberg
I saw it too and I hope it's going in the direction of First ** Encapsulation - getting rid of most if not all public field in Node, Way, Relation, and DataSet - providing a richer API for compound primitives like ways and relations, i.e. Relation::getReferringPrimitives() -> Set Way::is

[josm-dev] jttt and private class members

2009-07-28 Thread Dave Hansen
I've seen some SVN commits from jttt doing some refactoring of the Way.nodes. First of all, very cool stuff. I'd like to use this to make some of my ReverseLookup code and a bunch of the validator tests faster. What's the end goal of all of the churn, though? -- Dave _