It's been a while since the last time I blogged about impress.js. That's because after I completed adding a batch of long outstanding feature requests and pull requests, I felt somewhat content with the status of my impress.js fork.
The compelling feature of impress.js is to animate your presentations in a 3D space. Earlier this year I spent some time trying to move from placing my slides in a 2D plane to doing something really cool and 3D. But I never really got beyond some simple tilts and turns, like you see at the end of the official demo as well. Somehow I couldn't figure out the logic of simple rotations around x, y, and z axes.
During June-July I had pretty much completed adding the features that I myself had in mind impress.js (as you might have read on this blog back then). Some of those features of course had been asked for multiple times by others as well, in particular the ability to define slide positions relative to the previous slide, was a popular request, with several pull requests proposing it as well. Now that I've added such a plugin, I have to say it is indeed much more convenient way of authoring presentations.
With the Euro Cup 2016 done, evenings can again be spent contributing to my favorite open source project: The impress.js presentation framework. In the series of blog posts about my additions to it, it is now time to unveil a feature I added by popular request: Markdown support.
Last month I wrote about impress.js, and how I've started using it for my presentations. This has been going well, and during the past month I've actually given 2 more presentations using impress.js:
(You really have to click those links, embedding these presentations wouldn't make them justice!)
In terms of using an open source desktop, Sun releasing OpenOffice some 15 (?) years ago was an important milestone, comparable to Mozilla finally managing to produce a working browser in Firefox. It provided essentially feature parity with Microsoft office, and most importantly, decent compatibility with Microsoft's own proprietary file formats.
I've used OpenOffice, and now LibreOffice, for lots of non-trivial tasks, including writing a complete book. Sure, the UI toolkit was stuck in the 90's, and Sun wasn't really a good steward in pushing the code base into this century, but it did work.