emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: [dev] About a beamer back-end
Date: Fri, 15 Jun 2012 17:08:11 +0200	[thread overview]
Message-ID: <87ehpg8vfo.fsf@gmail.com> (raw)

Hello,

As I announced in another thread, I'm starting a Beamer back-end for the
new export engine.  Though, before I start hacking, I have a question
about environments.

I'm wondering if it is really interesting to have every environment set
up from headlines. I understand it allows to use column view but, from
my experience, I've used previous Beamer exporter without ever resorting
to this view.  Also, it introduces some hacks (like the "normal" block)
when you want to insert some text after a block.

On the other hand, I think special blocks could be used for
environments.  For example:

#+begin_src org
* Vocabulary
  
  #+ATTR_BEAMER: :title "Definition"
  #+BEGIN_BLOCK
  A *set* consists of elements.
  #+END_BLOCK

  Some text.

  #+ATTR_BEAMER: :title "Question." :action "<2->"
  #+BEGIN_ALERTBLOCK
  Let R be the set of all sets that are not members of themselves.
  Is R a member of itself?
  #+END_ALERTBLOCK
#+end_src

would result in:

#+begin_src latex
\begin{frame}
\frametitle{Vocabulary}
\begin{block}{Definition}
A \alert{set} consists of elements.
\end{block}

Some text.

\begin{alertblock}<2->{Question}
\end{alertblock}
\end{frame}
#+end_src

Beamer minor mode would provide templates for blocks instead of
shortcuts for property API.  Frames would still be defined from
headlines.

I do not mind keeping previous implementation, but it can be clunky at
times. What do you think?


Regards,

-- 
Nicolas Goaziou

             reply	other threads:[~2012-06-15 15:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 15:08 Nicolas Goaziou [this message]
2012-06-15 16:41 ` [dev] About a beamer back-end 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
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=87ehpg8vfo.fsf@gmail.com \
    --to=n.goaziou@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).