emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [dev] About a beamer back-end
Date: Wed, 20 Jun 2012 16:20:10 +0100	[thread overview]
Message-ID: <87fw9q6mdx.fsf@ucl.ac.uk> (raw)
In-Reply-To: <80oboedwpx.fsf@somewhere.org> (Sebastien Vauban's message of "Wed, 20 Jun 2012 13:55:06 +0200")

Sebastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:

[...]

> Personally, I dislike using headlines for *anything* that's in the frame. I
> like the idea that headlines do show the structure of your presentation:
>
> - (optionally) sections and subsections for the sidebar
> - frame title (and subtitle)
>
> and no more.

This is interesting because, for me, the blocks within a frame are very
much part of the structure of the presentation.  I often start writing a
presentation with the outline consisting of sections, frame titles and
block titles.

> I would add that headlines are inherently outline-oriented, while here we
> speak about block or column contents which are inherently block-oriented
> (maybe not really for the column contents, though).

But for me, block and column headings are part of the outline.

> But this whole thing is just personal taste. I'm not coming with any solution,
> however!

Yes, it probably all does come down to personal taste and, as I have
said in an earlier message, whatever Nicolas ends up implementing will
be fine with me.
-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.1.50.1 and Org release_7.8.11-69-ga2fd96

  reply	other threads:[~2012-06-20 17:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 15:08 [dev] About a beamer back-end Nicolas Goaziou
2012-06-15 16:41 ` suvayu ali
2012-06-15 16:47   ` Avdi Grimm
2012-06-18  7:50     ` Eric S Fraga
2012-06-18 12:35       ` suvayu ali
2012-06-19 13:21       ` Nicolas Goaziou
2012-06-19 21:04         ` Eric S Fraga
2012-06-20  6:23           ` Greg Tucker-Kellogg
2012-06-20 11:55             ` Sebastien Vauban
2012-06-20 15:20               ` Eric S Fraga [this message]
2012-06-21 14:37           ` Nicolas Goaziou
2012-06-21 14:51             ` Sebastien Vauban
2012-06-21 16:03               ` Nicolas Goaziou
     [not found]                 ` <87obocodo7.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-06-21 21:14                   ` **: " Sebastien Vauban
2012-06-25 22:39                     ` Andreas Leha
2012-06-21 14:55             ` Rasmus
2012-06-21 15:56               ` Nicolas Goaziou
2012-06-21 16:36                 ` Rasmus
2012-06-21 16:49             ` suvayu ali
2012-06-22  7:54             ` Eric S Fraga
2012-06-18  6:32 ` Daniel Bausch
2012-06-18 10:17 ` Rasmus
2012-06-18 10:35   ` Sebastien Vauban
2012-06-18 12:00     ` Rasmus
2012-06-28 10:40 ` Andreas Leha
2012-06-28 10:47   ` suvayu ali
2012-06-28 10:50     ` Andreas Leha

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=87fw9q6mdx.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.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).