Opened 8 years ago
Last modified 8 years ago
#12667 new enhancement
Ability to swtich between latest JOSM configs via swticher or via hotkeys
| Reported by: | openstreetmap.org-user-d1g | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: |
Description
Current usage of multiple configs is limited to command line parameters or (even worse) to deeply hidden load/save function (there no alternative to this in UI).
Switching from JOSM to command line wastes user time or users have to make non-trivial switchers in command line.
Attachments (0)
Change History (4)
follow-up: 2 comment:1 by , 8 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → needinfo |
comment:2 by , 8 years ago
Replying to Don-vip:
I don't understand what you're talking about?
Well closest equivalent of this feature is "perspectives".
Where user sees limited subset of tools each time (each perspective), but he could switch between perspectives. This feature is also found in Adobe products, but I don't know their term for it.
I think it is possible to implement using config reload in JOSM:
a user has a.xml config tailored to building infrastructure (extrude, building tools, etc; tags-heavy editing using toggle panels), submits data, then he switches back to railroad config b.xml (splines, parallel tools; tag-less editing based on styles and without toggle dialogs).
This feature is useful during heavy tracing: http://www.openstreetmap.org/user/Павел Яринюк/history - railroad feature/buildings/natural features. All of them need different subset of tools.
comment:3 by , 8 years ago
| Owner: | changed from to |
|---|---|
| Status: | needinfo → new |
comment:4 by , 8 years ago
admin_level editing is completely different from regular mapping in JOSM. There Validators solely to support admin_level editing.
turn lanes config is also different from anything else: https://github.com/mapbox/mapping/wiki/Mapping-guide-for-turn-lanes-from-imagery
While people have their specialization (custom config):
- there no possibility to switch between configs without leaving JOSM.
- there only one config in JOSM, newcomers have to learn how to create their solution every time or seek users who understand how to use them or share their configs with them.
Very few people understand how eclipse workspaces work (internally or how to create a custom workspace or simply have time to do this) or how to create a decent JOSM config tailored for one perspective.
It is also time-consuming, so it will be nice to have some variety of imperfect configs in default JOSM installation.
I don't understand what you're talking about?