[josm-dev] Tagging Presets

[Ulf Lamping]

Christoph Eckert schrieb:
> you even want a mechanism like "Gray out all menu entries which do not 
> fit the current selected data type" (to avoid mapping of nodes as 
> highway=residential, BTW there are a lot of them in the planet file - 
> thus its size ;-) .
>   
Hmmm, to be honest, I already thought to mention it - but not all in one 
go ;-)
> Most icons have blatantly been stolen from web resources like 
> commons.wikipedia.org. Most of them have been derived from SVG images 
> showing german road signs. Thanks to SVG it was relatively simple to 
> cut/copy/paste some stuff together. Inkscape can then export raster 
> graphics in the desired size.
>   
We might want to do this - later (there are more urgent things to do).
> A point worth a consideration. My personal opinion is that submenus are 
> a nightmare for average users. That's also one reason why I tried to 
> keep the most often used dialogs relatively simple. If those provide 
> proper TAB orders, respond to enter and ESC and maybe remember the last 
> used settings during a session, it should be possible to work 
> effectively with them.
>   
Yes, keeping the "last state" of the selections might be a way to handle 
this.

But submenus are very common on most software, so this shouldn't be a 
big problem for most users IMHO - unless the menu entry is so wide that 
you get problems to "stay in the row" while following the entry (this 
happens if one of the entry texts get's very wide).
>> Of course, this is not possible for the more
>> complex dialogs like the "Restrictions" dialog.
>>     
> This abbsolutely is the dialog I hate most, even that it's still 
> useful :) .
>   
At least for the drop-down entries: if such a dd entry with at most 4-5 
entries, better use a radio-buttons for this. This is *much faster* to 
work with and gives a much better overview about the available options 
(so it's a lot faster to "scan" the dialog by eyesight). BTW: this is 
also true for any of the preset dialogs if you don't want to use submenus.

One disadvantage of radio-button groups in this regard is that - if you 
have lot's of them in a dialog, this get's pretty ugly as there are no 
"columns". Usually you'll then use a grid layout (or however this is 
called in JAVA) to place these GUI elements in columns.

Regards, ULFL