From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [ANN] Beamer back-end for org-export in contrib/
Date: Sat, 30 Jun 2012 20:46:41 +0200 [thread overview]
Message-ID: <CAMXnza1thm3C8sYxdWWQAbOzhspK6Zomb9PFDJ4OaUZocDs+0g@mail.gmail.com> (raw)
In-Reply-To: <877guo26c9.fsf@gmail.com>
Hi Nicolas,
On Sat, Jun 30, 2012 at 4:59 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> 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". All accept options in
> 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. The former is translated as an overlay/action
> 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 ∀ \mathcal{R}
*** ignore :B_ignoreheading:
:PROPERTIES:
:BEAMER_env: ignoreheading
:END:
#+LATEX: }
> Every plain list has support for `:overlay' attribute (through
> ATTR_BEAMER affiliated keyword). Also, 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:
<http://www.texample.net/tikz/examples/connecting-text-and-graphics/>
> 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. As an example[fn:1],
>
> *@@e-beamer:<2->@@some emphasized text*
>
> will be translated as
>
> \alert<2->{some emphasized text}
>
Again, this works wonderfully.
[...]
> Also, on the minor changes list, syntax for BEAMER_THEME and alike is,
> for example:
>
> #+BEAMER_THEME: Rochester [height=20pt]
>
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.
next prev parent reply other threads:[~2012-06-30 18:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 14:59 [ANN] Beamer back-end for org-export in contrib/ Nicolas Goaziou
2012-06-30 18:46 ` suvayu ali [this message]
2012-07-02 12:22 ` Nicolas Goaziou
2012-07-04 1:30 ` suvayu ali
2012-07-04 16:08 ` Nicolas Goaziou
2012-07-04 16:26 ` suvayu ali
2012-07-05 11:56 ` Nicolas Goaziou
2012-07-07 10:04 ` suvayu ali
2012-07-07 12:32 ` Nicolas Goaziou
2012-07-07 12:56 ` suvayu ali
2012-07-07 12:58 ` Nicolas Goaziou
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=CAMXnza1thm3C8sYxdWWQAbOzhspK6Zomb9PFDJ4OaUZocDs+0g@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).