Re: Re: New beamer support

From: Darlan Cavalcante Moreira <darcamo@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: New beamer support
Date: Thu, 07 Jan 2010 11:39:38 -0300	[thread overview]
Message-ID: <4b45f234.8702be0a.68d2.ffffd38c@mx.google.com> (raw)
In-Reply-To: <87y6kab93a.fsf@mundaneum.com>

I don't think org-mode should try to detect when to use any of the frame options
in beamer. This could get into the way more then helping, specially the
allowframebreaks option.

In fact, the beamer manual tells you not to use the allowframebreaks option
except for long bibliographies (well, it also tells you not to use long
bibliographies) and I agree with this. In a presentation you have to choose
carefully what you will put in each slide and always leaving this to beamer with
the allowframebreaks is not a good approach.

In addition, I agree that when working in a presentation with org-mode you
compile much less, but you should still compile sometimes to see if the slides
are well designed. I don't know if Carsten has plans to implement this, but a
"fast preview" that exports and compiles only the current slide could be useful
here.

At last, I have a small feature request that would help organizing the
information among the slides. Right now you can use Alt+up/down arrow to move a
list item in a heading, but org does not allow passing beyond a heading
limit. This makes sense in a normal org file and is very useful, but when
writing a presentation with org this restriction can get into the way. This is
not a big deal, but maybe others are also interested in this.

- Darlan Cavalcante Moreira

At Thu, 07 Jan 2010 09:41:29 +0100,
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
> 
> Hi Carsten,
> 
> Carsten Dominik wrote:
> > On Jan 6, 2010, at 5:22 PM, Sébastien Vauban wrote:
> >> Carsten Dominik wrote:
> >>> there is now a new option org-beamer-frame-default-options
> >>
> >> When setting it into Emacs, great, it DOES WORK as expected!
> >>
> >> Though, I believe this is more a setting of the document itself, instead of
> >> one customization in my own `.emacs' file.
> >>
> >> I would rather like my colleagues to get the same output when compiling my
> >> document. I tried, then, the following:
> >>
> >> --8<---------------cut here---------------start------------->8---
> >> * COMMENT Setup
> >>
> >> # This is for the sake of Emacs.
> >> # Local Variables:
> >> # ispell-local-dictionary: "en_US"
> >> # org-beamer-frame-default-options: "[allowframebreaks]"
> >> # End:
> >> --8<---------------cut here---------------end--------------->8---
> >>
> >> with no success, though.
> >>
> >> Maybe I would have to try with a `#+BIND'.
> >
> > #+BIND will do the trick, it was made just for this.
> 
> #+BIND: org-beamer-frame-default-options "[allowframebreaks]"
> 
> does work.
> 
> 
> >> Though, wouldn't it be better to
> >> explicitly add something like:
> >>
> >> --8<---------------cut here---------------start------------->8---
> >> #+BEAMER_FRAME_EXTRA_OPTIONS: [allowframebreaks]
> >> --8<---------------cut here---------------end--------------->8---
> >
> > Yes, that would make sense if it is a frequently used feature.
> > I like to hesitate with introducing these special customizations
> > until I am convinced that this is used reasonably often.  Otherwise
> > I would have to have 1000 of the special lines, approximately.
> >
> > Question to all:  How likely is the use of a default option you'd
> > want to have on *every* frame?
> 
> The problem is similar to the `fragile' option. Either we can detect the
> "overflow" (and the automatically add the option only when needed), or we must
> add it everywhere in order to ensure we won't have text cut.
> 
> It's a bit different from when we directly edit beamer files. We compile often
> and we see the problem appearing.
> 
> Here, with Org, we would just work in Org only, and publish once at the end. A
> bit more easy to be aware that some text may have pass away.
> 
> As #+BIND works, I can imagine living quite honestly the way it currently is,
> but I let the others decide upon this.
> 
> Best regards,
>   Seb
> 
> -- 
> Sébastien Vauban
> 
> 
> 
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode