From: Rick Moynihan <rick@calicojack.co.uk>
To: sebastian_rose@gmx.de
Cc: "[emacs-orgmode]" <emacs-orgmode@gnu.org>
Subject: Re: Slides with Org
Date: Thu, 28 Aug 2008 11:32:44 +0100 [thread overview]
Message-ID: <48B67ECC.9070906@calicojack.co.uk> (raw)
In-Reply-To: <48B5D4DD.2000500@gmx.de>
Sebastian Rose wrote:
> Hi,
>
>
> Rick asked for Slides from Org-modes HTML export recently.
> While there is no real support slides in org-info.js, I
> still gave it try to have a poor mans slides.
>
> The main missing thing was the ability to navigate the
> section by clicking the window. This is now added and in
> the worg git.
>
> Please review and complain :-)
Before my 'complaints': Thanks a bunch, this is great!!! :-) The
org-mode continue to amaze me!
So, after taking a look at your example the first thing that jumps out
at me is the hack you've used to reveal individual bullet points one by one:
* Overview
+ Create the Org-mode file
* Overview
+ Create the Org-mode file
+ Export the Org-mode file to XHTML
* Overview
+ Create the Org-mode file
+ Export the Org-mode file to XHTML
+ Create a stylesheet for slides
Whilst this works, it doesn't seem entirely practical to duplicate the
content like this, particularly in a larger slide stack. Could we use
properties to control this? Reducing the previous outline to something
like this:
* Overview
:PROPERTIES:
:reveal: t
:END:
+ Create the Org-mode file
+ Export the Org-mode file to XHTML
+ Create a stylesheet for slides
Another suggestion, would be to offer more control over the title
heading. Currently it seems that the heading is always the #+TITLE:
rather than the current slides heading. A more sensible default would
be to render the slides title here, with an option to have it be the
presentations title.
It also seems that the double-clicking/sensitivity when returning to a
previous slide sometimes feels hard to perform. i.e. sometimes you
click too slow and progress forward rather than back. This may or may
not be something you have control over. As other's have suggested,
supporting the back/forward keys and spacebar for flicking through
slides would be nice too.
Another feature suggestion might be support for automated timings.
Where after loading a presentation pushing a button sets it off with
each slide being displayed for a specified time, according to an
overidable default (in seconds) e.g.
#+INFOJS_OPT: timing:30
With overiding supported through property drawers:
* Example of timings (whole slide takes 20 seconds)
:PROPERTIES:
:timing: 20
:reveal: t
:END:
+ Wait on this point for 10 seconds
+ Wait on this point for 10 seconds then push onto next slide
Finally, if possible, perhaps a class property could be used to control
which CSS class a slide is rendered with? This might allow better
control over certain slides where, for example you *ONLY* want a large
image to be displayed centred without a title etc...
As an aside, would it be possible to push org-info-js up into it's own
git repo, with the slides example you posted? Checking it out through
Worg is a mild pain, and it seems deserving of it's own repo.
> For REAL slides a different tool should be written (using jQuery
> or similar). Since slides are so different from 'normal' HTML, I
> guess they would blow the scripts size. If I think of slides, I
> think of efects.
Yes, effects and transitions would be a nice bonus and should be
achievable through libraries like scriptaculous and jquery...
Thanks again for your hardwork!
R.
next prev parent reply other threads:[~2008-08-28 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-23 3:24 org-info.js - new version with tags index Sebastian Rose
2008-08-26 10:04 ` Rick Moynihan
2008-08-27 22:27 ` Slides with Org Sebastian Rose
2008-08-28 1:30 ` Manish
2008-08-28 4:00 ` Wes Hardaker
2008-08-28 10:32 ` Rick Moynihan [this message]
2008-09-02 11:40 ` Carsten Dominik
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=48B67ECC.9070906@calicojack.co.uk \
--to=rick@calicojack.co.uk \
--cc=emacs-orgmode@gnu.org \
--cc=sebastian_rose@gmx.de \
/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).