From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: latex export and beamer columns
Date: Sun, 22 Nov 2009 12:12:26 +0000 [thread overview]
Message-ID: <878wdylpw5.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <3CB39269-FB18-4155-AF32-00F6B46F8061@gmail.com>
At Sat, 21 Nov 2009 14:34:18 +0100,
Carsten Dominik wrote:
>
> Hi Eric,
>
> this looks very nice! I just tried beamer for the first time,
> this is very simple now. Maybe I can drop powerpoint, at least
> for some stuff.
Thanks Carsten! Definitely drop powerpoint... I would highly
recommend org-mode to you ;-)
Seriously, the arguments for beamer versus PP are the same as (IMO)
latex versus Word and, for me, come down to text versus binary and
open versus proprietary...
> I think we need a good beamer tutorial on Worg, including this
> column stuff, and some text about image treatment.
>
> Any volunteers? Anything missing in Org that we should implement to
> support this better?
I may be able to help write such a tutorial (although not before xmas
as I'm bogged down with lectures [and hence my interest in getting
columns working in beamer!] at the moment).
At the moment, the only thing that is missing in org-mode to beamer is
some way to specify arguments to the \frame command, options such as
[shrink] or [t]. At the moment, there is no mechanism that supports
this. Something like attr_frame may be necessary just as we do with
figures, as in:
,----
| #+attr_frame: shrink=20
| *** This is a slide with a lot of text
| ...
`----
I have no idea how easy or difficult this would be to implement, mind
you.
There is also the issue of animation, specifically the <N> tags for
items in lists but most behaviour like this can be handled with \pause
statements so I'm not too worried about this.
next prev parent reply other threads:[~2009-11-22 12:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 12:49 latex export and beamer columns Eric S Fraga
2009-11-21 13:34 ` Carsten Dominik
2009-11-22 12:12 ` Eric S Fraga [this message]
2009-11-22 15:15 ` Eric S Fraga
2009-11-22 15:29 ` Matt Lundin
2009-11-22 19:31 ` Eric S Fraga
2009-11-23 13:55 ` Carsten Dominik
2009-11-23 22:15 ` Eric S Fraga
2009-11-24 0:02 ` Daniel Martins
2009-11-24 6:55 ` Carsten Dominik
2009-11-24 8:36 ` Eric S Fraga
2009-11-24 8:49 ` Eric S Fraga
2009-11-24 8:59 ` Carsten Dominik
2009-11-24 18:02 ` Eric S Fraga
2009-11-25 6:28 ` Carsten Dominik
2009-11-25 9:27 ` Eric S Fraga
2009-11-25 18:03 ` Eric S Fraga
2009-11-25 23:25 ` Carsten Dominik
2009-11-26 8:16 ` Eric S Fraga
2009-11-26 9:05 ` Carsten Dominik
2009-11-26 10:33 ` Eric S Fraga
2009-11-23 14:53 ` Sébastien Vauban
2009-11-21 16:33 ` Thomas S. Dye
2009-11-22 12:00 ` Eric S Fraga
2009-11-26 1:52 ` Łukasz Stelmach
2009-11-26 18:25 ` Eric S Fraga
2009-11-26 19:54 ` Darlan Cavalcante Moreira
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=878wdylpw5.wl%ucecesf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--cc=carsten.dominik@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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).