New save dialog has overflowing text & wasted space

[avarab@…]

The dimensions & design of the new save dialog are such that it has a lot of wasted space and some of the text can't be read due to it overflowing the UI elements.

See attached screenshot.

[avarab@…]

The new save dialog

[Gubaer]

And what would you like to have changed?

[avarab@…]

Replying to Gubaer:

And what would you like to have changed?

I'd like to have a dialog where all the text is readable and which doesn't take up too much space in proportion to the information it's displaying.

How exactly it should be designed I don't know. I just filed a bug to note the problem with the current one so that it's noted in the tracker.

[Gubaer]

Anyway, if you have some kind of sketch or scribble of what your ideal dialog would look like please post it here.

[xeen]

Not sure if that's a good idea: turn the table by 90 degrees. It uses the available space better in the common case, but might be confusing if there are two or more unsaved osm layers. On the other hand I can read timetables pretty easily so one might get used to it after having seen it a few times. Any comments on this?

[simon04]

I wouldn't change the orientation (turn by 90°). Filenames tend to be long and when having ⩾2 layers, more space is wasted than now.

Perhaps one could combine the columns "Should upload?" and "Upload": By default, "Upload" is checked whenever "Should upload?" is yes (is that correct?). When the default is changed, a (e.g. light yellow) background color could indicate/visualize that deviation. Thus, one could drop the columns "Should upload?" and "Should save?".

Btw, funny behaviour in r4337: I can drag the column headers to the left/right, but the content does not move (see attachment:drag_headers.png​).

[stoecker]

I think that dragging is nearly nowhere supported in JOSM, as we stayed on Java 1.5 for a long time. Nowadays either it should be disallowed or supported correctly. The later is better, disallowing is easier :-)

Reducing columns seems useful to me.

[xeen]

I had a different idea on how to design this dialog, but haven't looked into it. Since you can actually edit the save-to path in the dialog itself it probably will take more than one afternoon to update the dialog. Anyway, suggested layout:

+-----------------------------------------------------------------------+
| [IC ] *some OSM Layer* /(should be uploaded)/              [X] Upload |
| [ ON] save as: /click here to choose save path/            [ ] Save   |
|                                                                       |
| [IC ] *osmlayer2* /(should be uploaded) (should be saved)/ [X] Upload |
| [ ON] save as: /home/stefan/osm/osmlayer2.osm              [X] Save   |
+-----------------------------------------------------------------------+
| [Perform sel. actions before exiting] [Exit immediately] [Cancel]     |
+-----------------------------------------------------------------------+

with /italic/ and *bold* and the entries should alternate in background or be separated by a thin line.

[simon04]

Replying to xeen:

Wow, I like your suggestion very much! It gets away from the boring table and shows all relevant information to the user (in contrast to the current solution, which hides a lot in tooltips)!

[xeen]

You can try the WIP using this jar if you do not want to build yourself: ​http://goo.gl/Mr2Rk

Also, now is the time to ask for features ;)

[xeen]

The cursor is over the last cell. The "perform actions" button would be disabled, if upload was unchecked, too. If save was checked, the middle icon wouldn’t be greyed out.

[xeen]

suggested patch

[xeen]

The cursor is over the last cell. The "perform actions" button would be disabled, if upload was unchecked, too. If save was checked, the middle icon wouldn’t be greyed out.