emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bartholomaios Edessa <bartholomaios.edessa@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [whishlist] unified export template / property keys for presentations
Date: Thu, 13 Nov 2014 09:44:24 +0100	[thread overview]
Message-ID: <CAP65RffDJ9gu1H67jFyHok-Qdk2A3D=sY_ax5_m16pW-kh_Z1w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]

Hello,

orgmode has a nice interface for specifying things like frames, blocks,
quotes etc with org-beamer-mode and the special access keys (C-c C-b).

Although these serve only latex-beamer - and since orgmode has a lot of
non-beamer export options for presentations - I was wondering if we could
have something like this:

1) a function 'org-insert-presentation-template' that allows for different
basic options like type of transition, default heading depth for slides,
toc and so on.

2) a special minor mode 'org-presentation-mode' where more options can be
used by providing keybindings for inserting properties.

The main idea behind this is that it is perfectly fine for most
presentations to define at what heading level slides are, what font and
what colors org should use. All these things are basically similar in all
export backends for presentations and could therefore be handled by the
same set of options.

I guess that 80% of what the style and structure of a presentation consists
of would be covered by this, regardless of whether it is going to be a
beamer, s5, or reveal.js presentation.

This would make creating presentations a lot more user friendly. Because it
should not really matter whether or not I understand all the latex markup
that the export to beamer has to handle or the the html when using another
presentation export backend - for producing a quick and still nice-looking
presentation from an org-file.

What do you think?

[-- Attachment #2: Type: text/html, Size: 1672 bytes --]

                 reply	other threads:[~2014-11-13  8:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAP65RffDJ9gu1H67jFyHok-Qdk2A3D=sY_ax5_m16pW-kh_Z1w@mail.gmail.com' \
    --to=bartholomaios.edessa@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).