From mboxrd@z Thu Jan 1 00:00:00 1970 From: suvayu ali Subject: Re: [dev] About a beamer back-end Date: Fri, 15 Jun 2012 18:41:18 +0200 Message-ID: References: <87ehpg8vfo.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:41933) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SfZah-0004qJ-OW for emacs-orgmode@gnu.org; Fri, 15 Jun 2012 12:41:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SfZaf-0008Kx-Sf for emacs-orgmode@gnu.org; Fri, 15 Jun 2012 12:41:43 -0400 Received: from mail-ob0-f169.google.com ([209.85.214.169]:38836) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SfZaf-0008KV-L0 for emacs-orgmode@gnu.org; Fri, 15 Jun 2012 12:41:41 -0400 Received: by obbta14 with SMTP id ta14so4402133obb.0 for ; Fri, 15 Jun 2012 09:41:38 -0700 (PDT) In-Reply-To: <87ehpg8vfo.fsf@gmail.com> 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: Nicolas Goaziou Cc: Org Mode List 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 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.