At 2010-12-20 16:30, Frederik Ramm wrote:
I have had a client asking me to add a new type of preset user interface control for them, one where you can select multiple values from a list and this then ends up in a tag with a comma-separated list. Like so:

<multiselect key="colour" text="Colour" values="red,blue,green,yellow" default="" delete_if_empty="true" />

The user can then e.g. select "red" and "yellow" which creates the tag "colour=red,yellow".

It should be colour=red;yellow according to current usage.

I made some suggestions for expanding the existing preset syntax here: https://josm.openstreetmap.de/ticket/4901


The client would be ok with building this into JOSM proper. I am unsure - of course I'll happily contribute the code but in OSM we don't really want to encourage comma- (or semicolon-) separated tag values.

Really? They have become a fact of life, at least until/unless we make some significant tagging schema changes, which seemed more like hacks last time we discussed them.

--
Alan Mintz <[email protected]>


_______________________________________________
josm-dev mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/josm-dev

Reply via email to