#7184 closed enhancement (fixed)
Integrate ImproveWayAccuracy to core?
Reported by: | simon04 | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | ImproveWayAccuracy | Cc: | stoecker, bastiK, skyper |
Description
When are (good) plugins usually integrated to the JOSM core (e.g., the validator plugin)?
I consider the ImproveWayAccuracy plugin to be very useful for a broad audience (not only due to a broad availability of areal imagery). AFAIK, there haven't been any bugs nor changes to the plugin since 2011-05. The plugin only consists of 4 files and a total 871 loc.
Thus, I suggest to integrate ImproveWayAccuracy to the core.
Attachments (2)
Change History (40)
comment:1 by , 13 years ago
comment:3 by , 13 years ago
I'm not opposed, it's on par with "parallel way" and "extrude". The plugin doesn't rank very hight in the statistics, but this shouldn't be the only criterion.
comment:4 by , 13 years ago
Probably this is one of the cases, where a full working mode may be "expert"?
comment:5 by , 13 years ago
Replying to bastiK:
The plugin doesn't rank very hight in the statistics, but this shouldn't be the only criterion.
It took me very long (too long) long to find this plugin myself. This is not a kind of plugin, one actively searches for. As written above, due to the increasing availability of areal imagery, this plugin gets steadily more useful, IMHO.
Replying to stoecker:
Probably this is one of the cases, where a full working mode may be "expert"?
Is it? I would not consider improving the accuracy of existing OSM objects as "expert". To perform this task efficiently, this mode is very helpful.
follow-up: 7 comment:6 by , 13 years ago
Expert mode has the basic idea to ease the user interface for beginners. So a tool which allows a working mode, which also can be reached relatively easy with the standard methods clearly is "expert".
Actually the mode is "not beginner", but when labeling the normal mode "beginner" nearly everybody would click this off on the second day and the effect would be void.
The tool here is only interesting for people who no longer ask "Is this possible", but who ask "Can this be done faster" --> experts. :-)
follow-up: 9 comment:7 by , 13 years ago
Replying to stoecker:
The tool here is only interesting for people who no longer ask "Is this possible", but who ask "Can this be done faster" --> experts. :-)
Good point.
However, I consider the tools "create area" and "parallel copies" more advanced/complicated to use than "improve way accuracy". For beginners, there's probably also no need to have the mode "delete" as this can be done with [Del]
as well.
So we could add "improve way accuracy" to core first, and solve the (non-)expert classification of modes then?
comment:8 by , 13 years ago
I'd agree, that extrude mode and even delete mode are more "expert" then "improve way accuracy". I think it is crucial, to improve the expert mode switching - without restart and it should be easier to find (main menu).
comment:9 by , 13 years ago
Replying to simon04:
However, I consider the tools "create area" and "parallel copies" more advanced/complicated to use than "improve way accuracy". For beginners, there's probably also no need to have the mode "delete" as this can be done with
[Del]
as well.
All three should be expert options as well.
by , 13 years ago
Attachment: | 7184_hide.patch added |
---|
comment:10 by , 13 years ago
Patch hides DeleteAction, ExtrudeAction, ParallelWayAction by default. The shortcuts still work and the icons on the left hand side can be made visible by clicking on >>
.
Similarly, some of the toggle dialogs could be hidden on the left hand side (see also #6909).
What about my original question concerning ImproveWayAccuracy?
follow-up: 13 comment:12 by , 13 years ago
Replying to stoecker:
Go on with this patch and integration I would say.
When integrating ImproveWayAccuracy, does one have to look out for something?
comment:13 by , 13 years ago
Replying to simon04:
When integrating ImproveWayAccuracy, does one have to look out for something?
It should work :-)
Place stuff in proper directories, so it fits JOSM structure. I recently found a class in validator dirs, which actually belonged into commands.
comment:15 by , 13 years ago
I'd add the following files for the plugin (besides images):
- src/org/openstreetmap/josm/actions/mapmode/IWAGeometry.java
- src/org/openstreetmap/josm/actions/mapmode/IWATargetWayHelper.java
- src/org/openstreetmap/josm/actions/mapmode/ImproveWayAccuracyAction.java
Or is it better to have inner classes for the helper classes IWAGeometry, IWATargetWayHelper?
Is there a way to trigger an automatic uninstallation of the plugin ImproveWayAccuracy?
by , 13 years ago
Attachment: | 7184.patch added |
---|
comment:17 by , 13 years ago
Thank you for your guiding help. :-)
Here's the patch for integrating ImproveWayAccuracy. If it looks all right, I'll commit it tonight or tomorrow morning …
comment:18 by , 13 years ago
I'd rename IWATargetWayHelper.java to ImproveWayAccuracyHelper.java and merge IWAGeometry.java into org/openstreetmap/josm/tools/Geometry.java.
follow-up: 23 comment:21 by , 13 years ago
Please if possible also copy the help from OSM wiki to the online help at Help/Action/ImproveWayAccuracy and link to this page instead to OSM wiki from StartupPageSource.
comment:22 by , 13 years ago
Cc: | added |
---|
comment:23 by , 13 years ago
Replying to stoecker:
Please if possible also copy the help from OSM wiki to the online help at Help/Action/ImproveWayAccuracy and link to this page instead to OSM wiki from StartupPageSource.
Done.
follow-up: 25 comment:24 by , 13 years ago
Remaining: delete the plugin from the plugin SVN repository and from Plugins.
For the former, just issue a svn rm
?
comment:25 by , 13 years ago
comment:26 by , 13 years ago
Documentation needs to be updated due to r4850. When changing the shortcut, I prefer a key that is easily accessible with the left hand on a QWERT*-keyboard, e.g., [W]
would make sense, but then the building tool plugin shortcut has to move (see DevelopersGuide/ShortcutsList).
follow-up: 29 comment:28 by , 13 years ago
What should be the new shortcut for the building tool? It's challenging to find a free combination. [Shift]+[B]
?
comment:29 by , 13 years ago
Replying to simon04:
What should be the new shortcut for the building tool? It's challenging to find a free combination.
[Shift]+[B]
?
Why do not you use E instead of I then for ImproveWayAccuracy?
Also Utilsplugin2 action, used rarely (I added it), left side of keyboard. W is used very intensively when adding buildings.
follow-up: 31 comment:30 by , 13 years ago
The idea was to make the mapping more logical. [W]
has not much to do with buildings, and [E]
not much with improving way accuracy. I am aware that this way/will break the habit of users, but I expect that it may be beneficial for the long term.
follow-up: 32 comment:31 by , 13 years ago
Replying to simon04:
The idea was to make the mapping more logical.
[W]
has not much to do with buildings, and[E]
not much with improving way accuracy. I am aware that this way/will break the habit of users, but I expect that it may be beneficial for the long term.
Then a possible solution is to use W for improveWayaccuracy, leave B for buildingtools and move rarely used "Distibute nodes" to Shift-B.
comment:32 by , 13 years ago
Replying to akks:
Then a possible solution is to use W for improveWayaccuracy, leave B for buildingtools and move rarely used "Distibute nodes" to Shift-B.
That sounds good to me. The plugin buildingtools also has a shortcut for setting the building size.
comment:34 by , 13 years ago
[o27587] - buildings_tools: remap shortcuts ([B]
, [Ctrl]+[B]
) due to integration of ImproveWayAccuracy in JOSM core
comment:35 by , 13 years ago
I have commited building_tools binary from your source, setting JOSM version to 4855. There will be less shortcut conflicts...
follow-up: 37 comment:36 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
This seems to be fully finished.
comment:37 by , 13 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Replying to joshdoe:
This seems to be fully finished.
Plugin needs to be marked depreciated under wiki:/Plugins
comment:38 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Yes, it would be good (is harder for author to make changes in core, but there were almost no changes).