You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The old UI design is much more reasonable than the current one. (better utilization of screen space)
Most prominently, it does not recklessly invoke "Format" whenever "Run".
[ Quote rsc @ CE 2021-11-30 19:19:12 UTC: https://github.com/golang/go/issues/49829#issuecomment-982942522
... browsers rendered it as a desktop-sized site and then shrunk it down to fit the screen. That's clearly sub-optimal in general. ]
<^> While any more optimal approach doesn't seem to exist after all.
All attempts trying to create "mobile friendly" interfaces have, without a single exception: tremendously failed turning the interface outright into "general unfriendly".
[ Quote (previous):
A reasonably-sized font is preferable to a tiny unreadable font 99 times out of 100. ]
<^> While the exact standard determining "reasonably-sized" or "tiny unreadable" is illusive:
"tiny unreadable" for some may be "just appropriate" while "reasonably-sized" would be "giant bothersome".
.
Size of elements should be no larger than the minimum accessible extent, nor smaller: thus avoid clipping and thrashing (which also negatively impacts accessibility).
[ Quote rsc @ CE 2021-11-24 21:35:14 UTC: https://github.com/golang/go/issues/49769#issuecomment-978259981
in this incarnation of the playground, both input and output are now resizable windows - you can drag the bottom right corner, just like the GitHub box I'm typing this message into. ]
<^> Poor accessibility for touch screen. (same for the one on GitHub)
Probably should be considered a browser issue. (like the general handling on "mouseover" alike)
[ Quote mvdan @ CE 2021-11-24 11:12:53 UTC: https://github.com/golang/go/issues/49769#issuecomment-977774914
[ Quote fzipp @ CE 2021-11-24 00:39:48 UTC: https://github.com/golang/go/issues/49769#issuecomment-977320411
Another option is to split code and output vertically rather than horizontally. Code is usually longer than wide. ]
<^> I thought about that too, and while it would work great on wide screens like 16:9, it would be pretty bad for any form of vertical window or screen. Imagine opening the playground on a smartphone, for instance. ]
<^> Not necessarily. It may reside on an area that would require horizontal scroll to access [1].
[1] This does not mean it should be implemented through JavaScript-based drawer panels: which is suboptimal for this case.
The text was updated successfully, but these errors were encountered:
Related with this project [ https://github.com/MasterInQuestion/coordTransform ].
The old UI design is much more reasonable than the current one. (better utilization of screen space)
Most prominently, it does not recklessly invoke "Format" whenever "Run".
=== Related ===
[
|*| New Playground leaves little vertical space for the editor
|*| https://github.com/golang/go/issues/49769 ]
[
|*| "go.dev/play" UX regressions on mobile compared to "play.golang.org"
|*| https://github.com/golang/go/issues/49829 ]
----
[ Quote rsc @ CE 2021-11-30 19:19:12 UTC:
https://github.com/golang/go/issues/49829#issuecomment-982942522
... browsers rendered it as a desktop-sized site and then shrunk it down to fit the screen. That's clearly sub-optimal in general. ]
<^> While any more optimal approach doesn't seem to exist after all.
All attempts trying to create "mobile friendly" interfaces have, without a single exception: tremendously failed turning the interface outright into "general unfriendly".
[ Quote (previous):
A reasonably-sized font is preferable to a tiny unreadable font 99 times out of 100. ]
<^> While the exact standard determining "reasonably-sized" or "tiny unreadable" is illusive:
"tiny unreadable" for some may be "just appropriate" while "reasonably-sized" would be "giant bothersome".
.
Size of elements should be no larger than the minimum accessible extent, nor smaller: thus avoid clipping and thrashing (which also negatively impacts accessibility).
[ Quote rsc @ CE 2021-11-24 21:35:14 UTC:
https://github.com/golang/go/issues/49769#issuecomment-978259981
in this incarnation of the playground, both input and output are now resizable windows - you can drag the bottom right corner, just like the GitHub box I'm typing this message into. ]
<^> Poor accessibility for touch screen. (same for the one on GitHub)
Probably should be considered a browser issue. (like the general handling on "mouseover" alike)
[ Quote mvdan @ CE 2021-11-24 11:12:53 UTC:
https://github.com/golang/go/issues/49769#issuecomment-977774914
[ Quote fzipp @ CE 2021-11-24 00:39:48 UTC:
https://github.com/golang/go/issues/49769#issuecomment-977320411
Another option is to split code and output vertically rather than horizontally. Code is usually longer than wide. ]
<^> I thought about that too, and while it would work great on wide screens like 16:9, it would be pretty bad for any form of vertical window or screen. Imagine opening the playground on a smartphone, for instance. ]
<^> Not necessarily. It may reside on an area that would require horizontal scroll to access [1].
[1] This does not mean it should be implemented through JavaScript-based drawer panels: which is suboptimal for this case.
The text was updated successfully, but these errors were encountered: