From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [dev] About a beamer back-end
Date: Fri, 15 Jun 2012 18:41:18 +0200 [thread overview]
Message-ID: <CAMXnza2ngB=pbnLbofZeQzymoRmATpzA7kvgcqnw1VA8_M1aYA@mail.gmail.com> (raw)
In-Reply-To: <87ehpg8vfo.fsf@gmail.com>
Hi Nicolas,
First a big thank you for all your efforts over the last year.
On Fri, Jun 15, 2012 at 5:08 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>
> 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:
[...]
>
> I do not mind keeping previous implementation, but it can be clunky at
> times. What do you think?
I have to agree with you, the block approach seems cleaner to me.
Environments like definition or quotes appear on beamer slides as
blocks, so I think your proposal fits in better logically compared to
using headlines.
There is an added bonus to this, now headlines could be used properly to
do what it is meant to do, sectioning. Something like this would be very
nice:
#+begin_src org
#+BEAMER_FRAME_LEVEL: 3
* Top level section 1
** sub-section 1
*** frame 1
some intro text
#+ATTR_BEAMER: :title "Definition"
#+BEGIN_BLOCK
A *set* consists of elements.
#+END_BLOCK
some concluding text
** sub-section 2
*** another frame
* Top level section 2
** sub-section
*** some frame
#+end_src org
With this syntax it would be very easy to write both really long (40-50
frames) as well as quick and short presentations.
However this breaks backwards compatibility for existing org documents.
As a very frequent beamer export user I would be willing to break
backwards compatibility for cleaner structuring in the future. If
backwards compatibility is too precious, one could move org-beamer to
contrib and rename it org-beamer-lagacy.
Another comment/request I have is better support for overlays. It seems
to me with the block approach overlaying for blocks could be supported
with block header arguments (like babel). I'm not sure though how one
could have overlays in lists though. Maybe the [@n] syntax for ordered
lists could be exploited to support overlays with list (although I admit
it feels like a big hack)?
Hopefully these comments are helpful.
PS: I can't wait to test the new beamer exporter. :)
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2012-06-15 16:41 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 [this message]
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='CAMXnza2ngB=pbnLbofZeQzymoRmATpzA7kvgcqnw1VA8_M1aYA@mail.gmail.com' \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.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).