From: Matt Price <moptop99@gmail.com>
To: zwz <zhangweize@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: HTML5 presentations
Date: Wed, 24 Aug 2011 11:33:56 -0400 [thread overview]
Message-ID: <CAN_Dec_9HRq-9tRqXOHJNLkL4LXegeoRmdqrjicmoj4XZ8UWAg@mail.gmail.com> (raw)
On Wed, Aug 24, 2011 at 8:14 AM, zwz <zhangweize@gmail.com> wrote:
> Those days I came across two tools which I thought interesting and
> helpful if could be combined with org-export in some way.
>
> 1. Deck.js: a js lib for making modern html presentation. See
> http://imakewebthings.github.com/deck.js/#intro for more info.
>
I would really like to see an exporter for this, in part because
Drupal integration for deck.js is underway. We already have several
html5 presentation modes described on worg:
http://orgmode.org/worg/org-tutorials/non-beamer-presentations.html
but there are lots of html5 methods out there; here are some resources:
http://slides.html5rocks.com/#landing-slide
http://usepow.com/about/#
http://code.google.com/p/html5slides/
http://code.google.com/p/sfeir/source/browse/trunk/html5-slides/
so here are a couple of questions:
- is one of these frameworks better than/easier to work with than the
others? Can any of them be shared on slideshare or another archiving
service?
- can we standardize on a feature-rich exporter and start building a
useful interface to it (e.g., on e that allows users to specify
transitions & so forth in a property)?
- what would be the best starting point for a new exporter?
Jambunathan has the generic html exporter, surely that could be a
starting point? But the simple html5presentation exporter (see link
above) produces pretty good presentations already.
Anyway, I'm very glad to see these possibilities emerging in recent
months. I'm looking forward to the end of powerpoint! If I never have
to use OOo Present again it'll be too soon...
Matt
next reply other threads:[~2011-08-24 15:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 15:33 Matt Price [this message]
2011-08-25 22:38 ` HTML5 presentations Eric Schulte
2011-08-26 10:58 ` zwz
-- strict thread matches above, loose matches on Subject: below --
2011-06-07 18:56 Vinh Nguyen
2011-06-07 20:01 ` Tassilo Horn
2011-06-07 20:35 ` Eric Schulte
2011-06-08 7:21 ` Jambunathan K
2011-06-15 18:19 ` Eric S Fraga
2011-06-15 19:35 ` Eric Schulte
2011-06-15 20:57 ` Joost Kremers
2011-06-16 7:45 ` Eric S Fraga
2011-06-15 22:07 ` Juan Pechiar
2011-06-16 7:44 ` Eric S Fraga
2011-06-16 15:49 ` Achim Gratz
2011-06-17 19:35 ` Eric S Fraga
2011-06-18 7:09 ` Achim Gratz
2011-06-16 19:07 ` Robert Goldman
2011-06-16 19:29 ` Eric Schulte
2011-06-16 19:35 ` Robert Goldman
2011-06-16 20:36 ` Jambunathan K
2011-06-16 21:50 ` Robert Goldman
2011-06-16 23:19 ` Eric Schulte
2011-06-17 2:50 ` Jambunathan K
2011-06-17 1:09 ` Jambunathan K
2011-06-07 22:05 ` Christian Moe
2011-06-08 7:24 ` Tassilo Horn
2011-06-08 11:27 ` Rainer M Krug
2011-06-08 13:01 ` Tassilo Horn
2011-06-08 13:13 ` Rainer M Krug
2011-06-08 13:45 ` Tassilo Horn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAN_Dec_9HRq-9tRqXOHJNLkL4LXegeoRmdqrjicmoj4XZ8UWAg@mail.gmail.com \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=zhangweize@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).