From mboxrd@z Thu Jan 1 00:00:00 1970 From: suvayu ali Subject: Re: [ANN] Beamer back-end for org-export in contrib/ Date: Sat, 30 Jun 2012 20:46:41 +0200 Message-ID: References: <877guo26c9.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36504) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sl2hH-0000Vv-IH for emacs-orgmode@gnu.org; Sat, 30 Jun 2012 14:47:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Sl2hF-0000gN-Do for emacs-orgmode@gnu.org; Sat, 30 Jun 2012 14:47:07 -0400 Received: from mail-ob0-f169.google.com ([209.85.214.169]:53684) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sl2hF-0000fr-4U for emacs-orgmode@gnu.org; Sat, 30 Jun 2012 14:47:05 -0400 Received: by obhx4 with SMTP id x4so1445519obh.0 for ; Sat, 30 Jun 2012 11:47:01 -0700 (PDT) In-Reply-To: <877guo26c9.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, On Sat, Jun 30, 2012 at 4:59 PM, Nicolas Goaziou wrot= e: > Hello, > [...] > - Headlines become frames when their level is equal to > `org-e-beamer-frame-level' (or "H" value in the OPTIONS line). > Though, if an headline in the current tree has a "BEAMER_env" (see > below) property set to "frame", its level overrides the variable. The sectioning works wonderfully! [...] > On top of buffer keywords supported by `e-latex' back-end (see > `org-e-latex-options-alist'), this back-end introduces the following > keywords: "BEAMER_THEME", "BEAMER_COLOR_THEME", "BEAMER_FONT_THEME", > "BEAMER_INNER_THEME" and "BEAMER_OUTER_THEME". =C2=A0All accept options i= n > square brackets. > I tried a few of these out, works very well. [...] > Along with "BEAMER_env", headlines also support "BEAMER_act" and > "BEAMER_opt" properties. =C2=A0The former is translated as an overlay/act= ion > specification (or a default overlay specification when enclosed within > square brackets) whereas the latter specifies options for the current > frame ("fragile" option is added automatically, though). > I tried a few these too, works well. I recall you saying you would add more overlay support gradually; I would like to say it would be nice if there is support for replace-like overlays (e.g. \only or \onslide). It would be great if I can wrap blocks in these. To illustrate what I mean, I can produce the above effect with the following ugly hack: #+OPTIONS: H:2 * Section ** Frame title Some more text #+LATEX: \only<1>{% *** Example block :B_exampleblock: :PROPERTIES: :BEAMER_env: exampleblock :END: Some example text *** ignore :B_ignoreheading: :PROPERTIES: :BEAMER_env: ignoreheading :END: #+LATEX: } #+LATEX: \only<2>{% *** Theorem block :B_theorem: :PROPERTIES: :BEAMER_env: theorem :END: Some bla bla =E2=88=80 \mathcal{R} *** ignore :B_ignoreheading: :PROPERTIES: :BEAMER_env: ignoreheading :END: #+LATEX: } > Every plain list has support for `:overlay' attribute (through > ATTR_BEAMER affiliated keyword). =C2=A0Also, ordered (resp. description) > lists make use of `:template' (resp. `:long-text') attribute. > I wasn't clear what you meant here. Could you give an example? Did you mean I can specify overlay specification for list items with the above mechanism? I'm not clear on the syntax here. I have another feature request (for the distant future) with regards to lists; I would like to put tikz nodes in list items. I have tried that in the past with very limited success. For an example, you can look here: > Eventually, an export snippet with a value enclosed within angular > brackets put at the beginning of an element or object whose type is > among `bold', `item', `link', `radio-target' and `target' will control > its overlay specifications. =C2=A0As an example[fn:1], > > =C2=A0*@@e-beamer:<2->@@some emphasized text* > > will be translated as > > =C2=A0\alert<2->{some emphasized text} > Again, this works wonderfully. [...] > Also, on the minor changes list, syntax for BEAMER_THEME and alike is, > for example: > > =C2=A0#+BEAMER_THEME: Rochester [height=3D20pt] > I presume the beamer options go like the following? #+LATEX_CLASS_OPTIONS: [smaller,presentation] I have a question; are subtree exports supported yet? Great work! Cheers, -- Suvayu Open source is the future. It sets us free.