[josm-dev] UI development

[Gervase Markham]

Gabriel Ebner wrote:
> No, currently you can't directly edit a GPX layer.  You'd have to convert it
> to an OSM layer first.

Right. But once you do that, you manipulate the GPX points just like 
nodes? If so, we don't need specific operations for manipulating GPX points.

Even if it did become possible to directly edit GPX layers, you could 
still use the same operations as for nodes.

>> - Someone has added "Delete segment". I thought segments were no longer 
>> part of the data model?
> 
> Yes, the server knows of no such thing as a segment; however sometimes you
> want to delete just a part of a way:
> 
>     +----+----+----+----+----+
> 
> 		|
> 		V
>     
>     +----+----+    +----+----+

Aha. So this is basically equivalent to splitting the way at a node, 
then deleting one end of one of the ways?


      +----+----+----+----+----+

		|
  		V

      +----+----+ +--+----+----+

		|
  		V
      +----+----+    +----+----+

?

If so, I would suggest that it be done using this two-step process, 
unless it's a very common operation.

(Select node, press "S". This would split the way and select one of the 
two new nodes. So 50% of the time, you just press Delete; the other 50% 
of the time, you'd need to select the other node and press Delete.)

>> - Someone has added "Split ways with duplicating nodes at identical 
>> positions (yielding not connected ways)". I'm not quite sure what that 
>> means, but I thought that was how splitting a way would work. What other 
>> options are there?
> 
> Currently when you split a way at a node, you'll get two ways, and they'll
> share the node where you split them. 

Right. So is there any UI feedback at all that this operation has been 
completed?

When is it useful to be able to do this?

> What the OP wanted are two ways that
> don't share this node, i.e. duplicate the node and use one for the first way
> and one for the second.

OK.

> I'm actually quite comfortable using right-click for panning.  However I've
> always used JOSM with mice that have at least two buttons.  (Panning using
> left-click is probably more of an issue with mice that only have a single
> button.)

I'm currently suggesting Ctrl-click to pan on single-button machines, 
because apparently Ctrl-click is the standard Mac version of right-click.

Gerv