New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notes #1895
Conversation
|
Seems like a good approach to me. Would it be cleaner if note SVG elements were not classed |
| @@ -0,0 +1,85 @@ | |||
| iD.NotesLayer = function(context, dispatch) { | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This class is no longer used, right?
Yes, this is currently an icky point; needs CSS refactoring |
|
@samanpwbb Do you have thoughts on how notes should be shown with the map in iD? On osm they have hacky leaflet-esque markers with green/red colors. |
|
@tmcw as much as I'd like to restyle these to be better looking, I think the best approach right now is to make notes in iD as close as possible to notes in osm.org, for the sake of familiarity, and so the two can evolve together. |
|
Is this on hold now? |
|
Yes, iD's kind of in low maintenance mode currently. |
|
Just to poke things a little, as of an hour ago, josm-latest now has (very basic) note support built into core :) On a more serious note, it looks like iD is running into some of the same issues I did when adding note support to JOSM. Notes are part of the OSM API but are different from all other API objects in that they don't involve versions, tags or changesets. It does make things kind of awkward... |
Oh boy. This adds notes functionality to iD, this addressing #1393
Right now it takes the approach that:
Todos: