-
Notifications
You must be signed in to change notification settings - Fork 911
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
Make iD default editor #453
Conversation
Make iD the default editor for all users that have not specified a preferred editor, except fall back to P2 on IE.
What is the status with regard to the performance issues that prevented us doing this before (see #262 for the previous history). |
Initial tests suggest that performance (with Firefox 23) is much better than before. It's still a little slow if you have a lot of data loaded, but that can be improved by zooming in more. Of course this is on a fairly powerful desktop so I don't know what other people's experience will be like. |
Ignoring performance for a minute I just tried to use iD to add a couple of buildings and adjust a road and well frankly it's buggy as hell and so far I've been unable to complete anything. So the first attempt ended when I tried to move the end of a road and it wound up glued to my mouse pointer and nothing I did (single click, double click, return, escape, ...) would release it and allow me to carry on. The second and third attempts ended when the cursor got locked in the move mode (the hand icon) and nothing I did would change it and let me select anything. At this point, after three attempts I've managed to draw one building and delete two nodes from a road. At least the offline storage of edits makes reloading and continuing easy, but having to do that every 30s is not really a reasonable user experience. No way is this ready to be the default as it stands. |
This is not at all my experience with iD and I wonder what's going on. Could you report the problems you found together with browser and OS on https://github.com/systemed/iD/issues ? Let's get any concrete issues addressed and move on to the future. I think there's no disagreement that we want to get off of Potlatch 2. |
Raised openstreetmap/iD#1691 and openstreetmap/iD#1692 though I'm not sure they're very helpful... |
I believe the issues that @tomhughes encountered in Firefox are fixed in iD 1.1.4. If anyone finds otherwise, please let me know. |
Concerned that doing this before openstreetmap/iD#1646 is fixed will tie the sysadmin's hands for deploying katla/smaug |
And a few concrete proposals, drawn from discussions: |
Thank you for the summary @pnorman. Of the points raised against iD that you listed, the one that is a regression from Potlatch 2 is the lack of a copy/repeat tags feature (P2's 'R' keybinding). We plan to add this to iD, but I would argue that all things considered it's not something that should block a change of default. In the absence of any other clear bug reports that indicate a regression from Potlatch 2 I think we should merge this and make iD default for new users. I know there's been many good requests made but I don't think we can wait for a hard to define level of perfection to make iD default. The only hard bar we can measure against is the status quo we want to replace. iD is on par with P2 on all critical features and is much easier and safer to use overall. Let's flip the switch :) |
+1. I'd not only like this to happen because iD is objectively much better for the new user and for many editing cases, but also because it means that, as the maintainer of P2, I can start to gut all the newbie-friendly stuff that P2 has never done very convincingly, and refocus it as the intermediate-level editor for which it's much more suited. |
Could we get a test deployment so that we can test that fallbacks from iD to P2 in browsers iD doesn't support are working correctly? |
There is only one such fallback and it's pretty trivial so I'm not sure it's worth the effort. |
Okay, as far as I can tell the current regressions are Technical
User-facing
openstreetmap/iD#1646 is purely a technical timeline issue. If it gets fixed before we are ready to send map? requests to a slave server, no one will notice. If not, it could blow up badly the first time replication lag exceeds a second or so. openstreetmap/iD#1512 is on balance, probably not any reason to hold back. I think more users have expressed opposition to the Twitter and Facebook links than have used the twitter link in the last month. |
P2 has a Twitter link now so that's not a reason not to switch (whistles innocently). |
Not "much", and whether or not it's on balance any less obvious is debatable. In some ways they are more visible in P2, in others more visible (and protected) in iD.
By your own count there are about 30 unique users of the Twitter link per month. I count two users opposing any sort of social media sharing entirely and two or three wanting them less prominent or completely hideable. |
So I really don't see anything here that is a blocker, and performance wise it seems to be OK for me even on my laptop with Firefox 23, so I'm thinking that unless somebody has a very persuasive argument that we haven't already heard we should go ahead and merge this... |
👍 Tom. I was just playing around with the latest iD on my older Core 2 Duo Linux laptop and it was noticeably faster than the last time I tried. Very usable. |
+1 the iD |
Merged. |
This makes iD the default editor on OSM. It's already the first option in the drop down, but this PR makes iD the editor that users land in when they just click the "Edit" label.
I hope to get this merged, now that initial concerns were addressed with the 1.1. release of iD that was just rolled out on OpenStreetMap.org: