31–40 of 98 posts
Shameless plug: I'm a lecturer and have scratched this itch some time ago with a pet project that a couple lecturers are using now: https://github.com/munen/p_slides/ It doesn't ship it's own editor, because everyone already has a favorite(for me that's formerly vim, now Emacs). It's only static files, so it doesn't need a server or pre-compilation. It's extensible, has syntax highlighting and produces PDFs for the s…
Shameless plug: I'm a lecturer and have scratched this itch some time ago with a pet project that a couple lecturers are using now: https://github.com/munen/p_slides/ It doesn't ship it's own editor, because everyone already has a favorite(for me that's formerly vim, now Emacs). It's only static files, so it doesn't need a server or pre-compilation. It's extensible, has syntax highlighting and produces PDFs for the s…
a) looks cool b) i would be much more interested if the "example presentation" actually showed me a presentation, not some raw html. maybe use GitHub Pages to through up an example?
b) Very good point. I just made it so that you can now click on the example and see it unfold in your browser without having to clone the repo. Thank you for the feedback!
Shameless plug: I'm a lecturer and have scratched this itch some time ago with a pet project that a couple lecturers are using now: https://github.com/munen/p_slides/ It doesn't ship it's own editor, because everyone already has a favorite(for me that's formerly vim, now Emacs). It's only static files, so it doesn't need a server or pre-compilation. It's extensible, has syntax highlighting and produces PDFs for the s…
How is it compared to reveal.js? http://lab.hakim.se/reveal-js/
* reveal-js is _much_ bigger whereas p_slides relies on well tested and established software. For example many features that you can find on the reveal-js README are also included in p_slides, because it uses W3Org slidy-js[1]. p_slides actually is only very little code itself as it glues together very well established and good existing libraries. reveal-js does a lot by itself. Both options are valid, yet they are different(;
Slide authoring supports nearly all of Deckset syntax (plus a few more tokens), slide configuration and custom themes.
I like the approach of creating a single static file (i.e. no JavaScript).
An advantage of creating ODP files is that the whole reusable presentation is one file. PDF is not as friendly for reuse. The presentation author that uses Marp could publish a git repo or a zip file with the source files.
A big advantage of HTML and PDF is that they render directly in the browser. ODF support in browser is a still a dream for the future.
The author of odpdown is a contributor to LibreOffice.
Shameless plug: I'm a lecturer and have scratched this itch some time ago with a pet project that a couple lecturers are using now: https://github.com/munen/p_slides/ It doesn't ship it's own editor, because everyone already has a favorite(for me that's formerly vim, now Emacs). It's only static files, so it doesn't need a server or pre-compilation. It's extensible, has syntax highlighting and produces PDFs for the s…
How is it compared to reveal.js? http://lab.hakim.se/reveal-js/
I like the way our tools went from Text -> Graphical interface -> Text You can see this with all the CLI tools being introduced for traditional programs. I suppose people appreciate control and automation.
Reminds me of Neal Stephenson’s great essay, ”In the Beginning Was the Command Line”. http://cristal.inria.fr/~weis/info/commandline.html
If someone else wants to read that more comfortably later tonight: https://www.dropbox.com/s/143tu70gxc40qvi/In.The.Beginning.W...
_(no guarantee on the conversion quality)_