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 students. Also, it's only a mash up of great existing libraries, so it needs no maintainance and further development. One of the few pieces of software that I wrote which are feature complete^^
A couple friends(also lecturers) and I have been using it for about five years now.
Are you aware of markdeep?
...support for it might be a nice addition to this project.
Markdeep looks totally awesome - I'm going to give it a try, soon! Now is midnight, though, and my fiance wants me to quit the computer^^
Thanks again, I'm looking forward to be able to include diagrams and have them under version control!
* 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. 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(;
S9 really looks nice - however, it is not self contained in the sense that I was referring to. p_slides is essentially a single HTML file (with the other assets hosted somewhere).
For S9, Ruby and usage of the command line is required. For a developer, that's not a big issue, of course. Myself, I'm a Ruby/JS/Clojure dev, so I do not mind installing one more gem(; However, my goal was to _really_ make p_slides self-contained. There is no need to install anything, run any pre-compiler or run the slide within a web-server. It doesn't even use npm or bower to install the assets. With this methodology, p_slides certainly is technologically less complex (or interesting^^), but it continues to work after years without any change on any computer that has a browser. That's just not happening with Ruby or Node or any other dependency. I'm not saying the latter is bad (it is not at all!), I'm saying this simplicity ability to be completely self-contained with no tooling required was the specific design decision for p_slides and it served me and a couple lecturers well. I basically made no advertisement for it, I just wrote it, because I wanted something that just works and I can distribute to students, too.
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!
My hacked up slide system (which I want to dump, I hacked someone else's library years ago) makes a fixed div of size 1024x768, and then uses CSS zoom to resize that to the browser window.
I'm also using it on OS X and Debian. Both work well. And as is recognizable from the git commit history - there's not much that needs to be done over the years to keep it going. Exactly my kind of HTML system - dead simple, no dependencies, works also years later^^
With PowerPoint / keynote and friends, I can be sure all my text will fit on the screen, even if I end up on a stupid 800x600 projector. No HTML framework, except my hacky mess, seems to do that. Maybe resizing mid presentation bothers other people less than me.
Would you be willing to share your hacky mess or make a PR? I really do get what you're referring to now and do think that if you won't contribute, I'll have to write my own hacky mess(;
hovercraft looks nice, though - I'll probably check it out later on a bigger machine, again. Thanks for sharing!
You can see this with all the CLI tools being introduced for traditional programs. I suppose people appreciate control and automation.
If someone else wants to read that more comfortably later tonight:
_(no guarantee on the conversion quality)_
But I cannot see how you can love Markdown. A shit standard that uglifies everything it touches, instead of celebrating the beauty of typography.
There is no inconsistency between liking command line, and being demanding in terms of text layout. Just ask LaTeX.
If you wrote documents in word 1.0 or WordPerfect or something, they may be lost to the world but markup could still be read by any reader.
Example of use: https://speakerdeck.com/thbar/de-rails-a-phoenix-retour-dexp...
It's uses markdown as well, has a presenter mode, speaker notes, and is easily customizable. The best thing is that everything can neatly fit in an HTML file or you can create a folder with the JS for offline usage.
And no, I don't argue that NIH doesn't exist in other suckless projects, merely that it isn't the rationale for sent. Sent has some solid advantages over anything else out there, at least for me.
HN is a lot like Youtube comments: There's a lot of arguing, but sometimes, people treat each other decently. It's honestly kinda surreal, coming from 4chan, reddit, or tumblr.
(Using just "---" to separate slides instead of repeating:
slide markdown goes here
...seems like a productivity win IMO)
pandoc hello.md -t revealjs -o hello.html
Looks like either top level headings (equivalent to sections I guess) or a line like this "----------" would work.
My personal example: http://slides.mkii.org/#/1
I've been working for a bit on a project for converting mind maps into slides. One feature I really liked was changing the level of depth of items.
Let me try to explain what I mean. Say you're brainstorming and create a tree/toc of your slides. Then you start filling in the items for each slide. While you're doing so, you realize that slideA requires more details, so you turn the slide into a section and it's items into slides. Similarly, another section with multiple slides becomes less important, so you turn that section into a slide slideB and its slides into items of slideB.
The reason I like mind maps/trees is that these operations can be easily done by changing the level of depth of the items, e.g. via drag & drop.
I really like this idea of a simple markup for creating slides (plus the fact that it's text, so easy to version), and if this feature of making easy to change the level of depth of items could be integrated I think this would be a super plus!
I used to think text was the future for making slides, but then I realized I cared too much about exactly how my slide looked, and a WYSIWYG saves a ton of time if you want that level of control.
I'm not complaining about this project...I'm just commenting about why no "production" course developers would consider switching to something like this. Just an FYI.
It generates presentations from markdown with reveal.js and beamer. It also generates documents both HTML and PDF.
I've been using Bespoke.js . Minimal core, and drop in plugins as needed. I also made a skeleton for quickly making new decks .
I don't know if that's the only option or if there are more than that.
Otherwise, this application is simple and to the point for making quick slide sets. I wonder if someone will invest the time to make a Go-lang style slide theme.
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.
If I have one critique from growing the docs: I find myself giving presentations on the fly. I hack around on Google Slides until the last minute and throw up a link so that I can share with the rest of the world, but also so that I can use any Internet connected computer to present. With revealjs, I get both local and easy-to-S3 access. I may have missed it but can Marp slides be ported so that other computers can run the presentation without installing the app?
Slide authoring supports nearly all of Deckset syntax (plus a few more tokens), slide configuration and custom themes.
Note that Sourceforge was down when I checked, but this should be the right URL.
(yhatt) Yuki Hattori
- rename tarballs to Marp-0.0.8...tar.gz
- put the code inside a main directory
Markdown represents, honestly, the massacre of the art of typography. It is ironic how such an ugly standard clashes with the its inventor's purported love for Apple, a company whose very DNA is about the beauty of layout, fonts, and the visual representation of the written word.
Markdown -> you have been weighed in the balance and found (severely) wanting.
In the case of using markdown for generating web based presentations, your CSS would be responsible for the styling - just like any other web page.
Markdown is just the semantics and content.