From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bartholomaios Edessa Subject: [whishlist] unified export template / property keys for presentations Date: Thu, 13 Nov 2014 09:44:24 +0100 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1134c518f7bf190507b98471 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49557) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xoq0w-0001k0-IN for emacs-orgmode@gnu.org; Thu, 13 Nov 2014 03:44:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xoq0v-00018b-HC for emacs-orgmode@gnu.org; Thu, 13 Nov 2014 03:44:26 -0500 Received: from mail-qc0-x230.google.com ([2607:f8b0:400d:c01::230]:64890) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xoq0v-00018U-C8 for emacs-orgmode@gnu.org; Thu, 13 Nov 2014 03:44:25 -0500 Received: by mail-qc0-f176.google.com with SMTP id x3so10785260qcv.35 for ; Thu, 13 Nov 2014 00:44:24 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --001a1134c518f7bf190507b98471 Content-Type: text/plain; charset=UTF-8 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? --001a1134c518f7bf190507b98471 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

org= mode 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 h= ave something like this:

1) a function 'org-insert-present= ation-template' that allows for different basic options like type of tr= ansition, 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.

T= he main idea behind this is that it is perfectly fine for most presentation= s 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=20 would be covered by this, regardless of whether it is going to be a=20 beamer, s5, or reveal.js presentation.

This would make cr= eating 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 expor= t backend - for producing a quick and still nice-looking presentation from = an org-file.

What do you think?

=
--001a1134c518f7bf190507b98471--