3 ms·
The content of the slides is good/informative.. but the UI for the slides is terrible. I didn't know where to click, I tried clicking on the slide next to it...
by rgbrenner 13y ago
The content of the slides is good/informative.. but the UI for the slides is terrible. I didn't know where to click, I tried clicking on the slide next to it... tried dragging the slide over, and selected a bunch of text. Clicked a few other parts of the screen.. Then it occurred to me to try the arrows. If I hadn't thought of that, I would have just left.
Why would you design something like that? At least give people instructions.
- tokenizerrr 13y agoClicking on the next slide works fine for me, and it was the first thing I tried.
- sciurus 13y agoYou have to click on the left third of the next slide, or the right third of the current slide.
- 4ad 13y agoI'm pretty sure you can't drag slides over in Powerpoint either. It's a tool for the presenter, the guy giving the talk, not for you, guy on the Internet. It's HTML 5, so it's easy to share with you or with the audience, but he is the user of the tool, not you. /edit: https://groups.google.com/d/msg/golang-nuts/X9z59NxSvtg/Sj0CQk_C1HYJ https://groups.google.com/d/msg/golang-nuts/X9z59NxSvtg/Sj0C...
- jerf 13y agoAs a NoScript user, I sometimes try to explain to people that for every site ruined by NoScript, there's another site that's made easier to use. This would be one of the examples of the latter. I just got a nice HTML text-ish file with headers for the slides.
- joblessjunkie 13y agoIt's also basically impossible to read on an iOS device.
- vanderZwan 13y agoYou make a valid point about usability from the point of view of viewing the slides online. However, it wasn't designed for that, but as a tool by the Go authors to be able to quickly churn out presentations in a simple markup language and run code from within the presentation similar to how play.golang.org works. There's a presentation on that, actually[1] The assumption is that if you use this software you'll read the instructions and know how to use it. In other words, being able to put it online was an afterthought. Not that this isn't a fixable problem. TL;DR: historical reasons, designed for different usecase, can be fixed. [1] http://talks.golang.org/2012/go-docs.slide#20 http://talks.golang.org/2012/go-docs.slide#20