5 ms·
Off topic: Why are their slides so unusable on iPad!? I can't swipe to the next slide without skipping that and 3 others.
by AndreasFrom 14y ago
Off topic: Why are their slides so unusable on iPad!? I can't swipe to the next slide without skipping that and 3 others.
- deleted 14y ago[deleted]
- jlarocco 14y agoThey're annoying in a regular desktop browser, too. I don't know why people feel they need to break regular scrolling for their slides. I'm sure it's interesting content, but I'll wait for a PDF version of the slides.
- 4ad 14y agoTell me when the PDF version has embedded, runnable code snippets.
- masklinn 14y ago> Tell me when the PDF version has embedded, runnable code snippets. When you're making the basic task of seeing the slides impossible, nobody cares about your pointless turd-polishing. Furthermore, PDF readers (at least Adobe's, but third-parties also sometimes do even if not all APIs are present) embed an ECMAScript interpreter, so you can indeed have embedded runnable code snippets in PDF: http://www.adobe.com/devnet/acrobat/javascript.html http://www.adobe.com/devnet/acrobat/javascript.html
- 4ad 14y ago> When you're making the basic task of seeing the slides impossible, nobody cares about your pointless turd-polishing. These are slides for the presenter. Nobody cares if you see them or not. Only the presenter has to care. > PDF readers [...] embed an ECMAScript interpreter So you wrote a Go to Javascript compiler? Can the VM running in the PDF reader implement a web server that can interact with the outside world?
- masklinn 14y ago> These are slides for the presenter. [...] Only the presenter has to care. Irrelevant, the whole thread of inquiry is about seeing the slides locally, you're two comments too late to try that one: you implicitly acknowledged the desire and desirability of personally viewing the slides in your previous comment. > So you wrote a Go to Javascript compiler? Also irrelevant (although there likely is no need to, there's an LLVM Go frontend and there's emscripten), the exact same method used here can be used there. > Can the VM running in the PDF reader implement a web server that can interact with the outside world? That doesn't even remotely make sense.
- jlgreco 14y agoI think you are getting a bit too aggressive about some slides with poor UI. You are asking a lot of the slide authors to minor facilitate secondary usage at the expense of primary usage. It could be a lot worse, they could be like 99% of the other slides in the industry: completely worthless without listening to the accompanying lecture.
- chimeracoder 14y ago> You are asking a lot of the slide authors to minor facilitate secondary usage at the expense of primary usage. I'm in a desktop browser, and I find this incredibly annoying to navigate. If that's not "primary usage" for viewing slides posted online, I don't know what is.
- burntsushi 14y ago> If that's not "primary usage" for viewing slides posted online, I don't know what is. Seriously? The primary usage is presentation..........
- jlgreco 14y agoPrimary considerations are centered around the presenter himself. He is the primary user of the slides, so whichever system he is most comfortable with will be the obvious choice. Asking that the presenter dedicate less time to preparation and more time to constructing some sort of elaborate LLVM/emscripten PDF presentation just for the benefit of secondary users who won't/can't use arrow keys is fairly unreasonable.
- duaneb 14y agoIt doesn't matter if they have runnable code if I can't get to it.
- gizzlon 14y agoOf course is does.. Most other people can get to it
- mseepgood 14y agoThe 'present' tool is open source, you can improve it if you have some JavaScript skills: http://code.google.com/p/go/source/browse/?repo=talks#hg%2Fpresent http://code.google.com/p/go/source/browse/?repo=talks#hg%2Fp... Here's the touch event handling code: http://code.google.com/p/go/source/browse/present/static/slides.js?repo=talks#259 http://code.google.com/p/go/source/browse/present/static/sli...
- enneff 14y agoYes, someone, please do this. I am the author of present, but I just pulled slides.js from another slide deck software. It's on my list to try to fix this, but I have little experience with touch devices. I'm sure someone with experience writing UI code for touch devices could make quick work of this.