Modify

#6741 closed enhancement (fixed)

[Patch] Improve Advanced Object Info

Reported by: simon04 Owned by: team
Priority: normal Component: Core
Version: Keywords:
Cc:

Description (last modified by simon04)

I adapted the Advanced Object Info dialog to increase readability. The output is very similar to http://www.openstreetmap.org/browse/.

Any comments?


Attachments (3)

6741.patch (17.5 KB) - added by simon04 21 months ago.
inspect.png (45.2 KB) - added by simon04 21 months ago.
6741.v2.patch (18.0 KB) - added by simon04 21 months ago.

Download all attachments as: .zip

Change History (14)

Changed 21 months ago by simon04

Changed 21 months ago by simon04

comment:1 Changed 21 months ago by simon04

  • Description modified (diff)

comment:2 follow-up: Changed 21 months ago by bastiK

Looks better, IMHO.

Minor things:

  • Why remove the sorting of the primitives?
  • The indentation for 'modified', 'deleted' and conflicts looks strage.
  • i18n: The strings for translation are collected by a script that scans the source code for tr(...) and marktr(...) with string literals as arguments. So something like s="modified"; add(tr(s)); does not work.

comment:3 Changed 21 months ago by stoecker

So something like s="modified"; add(tr(s)); does not work.

It must be "s=marktr("modified"); add(tr(s));" :-)

comment:4 in reply to: ↑ 2 ; follow-up: Changed 21 months ago by simon04

Replying to bastiK:

  • Why remove the sorting of the primitives?

I worked on this patch before your commit. I have no strong opinion on this point. When sticking to the order of selection (w/o sorting), it gives more control to the user.

I'll adapt the patch to reflect your suggestions. Better committing after the stabilization phase?

comment:5 in reply to: ↑ 4 Changed 21 months ago by bastiK

Replying to simon04:

Replying to bastiK:

  • Why remove the sorting of the primitives?

I worked on this patch before your commit. I have no strong opinion on this point. When sticking to the order of selection (w/o sorting), it gives more control to the user.

The selection comes from a HashSet, so order is randomized.

Better committing after the stabilization phase?

Yes, unless you feel strongly about getting it into next tested.

Changed 21 months ago by simon04

comment:6 Changed 21 months ago by simon04

I integrated your comments from above … I assume that I can commit this patch after the stabilization phase.

comment:7 Changed 21 months ago by bastiK

Sure, go ahead.

Maybe we can improve display of conflicts?

Node: 739410997
  State: modified
  Data Set: 2c390c
  Edited at: 2011-09-06T10:15:06Z
  Edited by: alv (4660)
  Version: 3
  In changeset: 9225884
  Tags: 
    "capacity"="9"
    "description"="pyöräteline"
    "amenity"="bicycle_parking"
  Coordinates: 60.2195182, 25.0042714
  Coordinates (projected): 2783462.7599048135, 8448774.202314496
  In conflict with: 
Node: 739410997
  State: modified
  Data Set: 1f3b536
  Edited at: 2011-09-06T10:15:06Z
  Edited by: alv (4660)
  Version: 3
  In changeset: 9225884
  Tags: 
    "capacity"="8"
    "description"="pyöräteline"
    "amenity"="bicycle_parking"
  Coordinates: 60.21942278701698, 25.00446350188961
  Coordinates (projected): 2783484.1445893454, 8448752.817629961

comment:8 follow-up: Changed 21 months ago by simon04

Replying to bastiK:

Maybe we can improve display of conflicts?

Of course, what do you suggest? Probably In conflict with Node: 739410997 (cf. your example)?

comment:9 in reply to: ↑ 8 Changed 21 months ago by bastiK

Replying to simon04:

Replying to bastiK:

Maybe we can improve display of conflicts?

Of course, what do you suggest?

Not sure, but looks a little strange right now.

Probably In conflict with Node: 739410997 (cf. your example)?

Ok, and with 0 indentation for that line?

comment:10 Changed 21 months ago by bastiK

Minor stuff:

  • Would be nice, to display number of nodes / members, for ways and relations.
  • For way nodes, you don't need the prefix Node: in each line.
  • Role should be in quotes.

comment:11 Changed 21 months ago by simon04

  • Resolution set to fixed
  • Status changed from new to closed

In [4410/josm]:

fix #6741 - improve Advanced Object Info - feel free to enter any suggestion/comment to the existing ticket

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed .
as The resolution will be set. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.