Karl wrote:
Exactly, and just for the sake of naming suggestions: in this context they
could be called NodeMemento, WayMemento, etc.
(really just for the sake of examples, I'm not in favor of these names, they
would be used in the context of undo/redo, but not in the general context of
OSM
Jiri,
Jiri Klement wrote:
I'm working on support for referrers and I run into a problem which
I'm not sure how to fix.
Can you explain (or point me to a previous post that explains) what
referrers are good for?
Currently JOSM quite often makes copies of
primitive (using for example
Hi,
Jiri Klement wrote:
OsmPrimitive is no longer just a storage for osm data. It has (will
have) methods that will automatically update referrers, spatial index
and other things. We need another class that will just hold data -
that's what PrimitivePrototype is for.
Is the traditional setup
. Oktober 2009 19:29
An: Frederik Ramm
Cc: josm-dev
Betreff: Re: [josm-dev] Problem with referrers
On Mon, Oct 5, 2009 at 9:43 AM, Frederik Ramm frede...@remote.org wrote:
Can you explain (or point me to a previous post that explains) what
referrers are good for?
For example when way has list
Hi Jiri
What do you think about that? Can you think of any problems this might
bring us?
I can only think of adavantages. The data classes I've added for managing
the history of primitives could possibly be replaced with *Prototype too.
The second approach (turning dataset into a factory for
