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!