From: Carsten Dominik <carsten.dominik@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: New beamer support
Date: Wed, 6 Jan 2010 11:06:58 +0100 [thread overview]
Message-ID: <4D2A7250-E096-4B8D-A7F0-85B043F01D08@gmail.com> (raw)
In-Reply-To: <871vi3bm62.fsf@mundaneum.com>
On Jan 6, 2010, at 10:46 AM, Sébastien Vauban wrote:
> Hello all,
>
> Here a few comments, after my first attempt with the new beamer
> support --
> excellent, needless to say...
>
> Before that, I was using Nick's export class. But, now, I'm using
> yesterday's
> git version.
>
> The few things I'm tackling right now are:
>
> - How to get a TOC with a frame title, without having to add it
> explicitly?
What would you like to have the LaTeX to be like?
>
> - How to get alerted text, without customizing `org-export-emphasis-
> alist'?
> Has this been forgotten from the commit?
I don't remember this. Can you please remind me?
>
> - How to get "frame breaks", without modifying the resulting TeX
> file (by
> adding a frame option `allowframebreaks' -- similar to the `fragile'
> option)?
Just put [allowframebreaks] into the :BEAMER_envargs: property of
the node that becomes the frame.
>
> - How to get the TOC repeated when changing of section, with the new
> item
> highlighted? See my manual essay ;-)
I don't know! Isn't this something that can be done with beamer themes?
I have no idea.
>
> The last question has maybe few to do with Org. I mean: maybe, we
> can't have
> that feature implemented in Org. Dunno.
Beamer support is hacking Org quite a bit, installing hooks left
and right, so I think it can be done. But I would need o know what
exactly is needed/wanted....
- Carsten
>
> Here follows an example to play with, and see what I'm talking about:
>
> --8<---------------cut here---------------start------------->8---
> #+TITLE: Inventory
> #+AUTHOR: Seb Vauban
> #+EMAIL: no@one.com
> #+DATE: 2010-01-06
> #+DESCRIPTION:
> #+KEYWORDS:
> #+LANGUAGE: en
> #+OPTIONS: H:2 num:t toc:nil
> #+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:t tags:not-in-toc
>
> #+LaTeX_CLASS: beamer
> #+LaTeX_CLASS_OPTIONS: [presentation,t]
> #+BEAMER_FRAME_LEVEL: 2
> #+BEAMER_HEADER_EXTRA: \usetheme{Madrid}\usecolortheme{default}
> #+COLUMNS: %30ITEM %8BEAMER_env(Env) %7BEAMER_opt(Options)
> %6BEAMER_dovl(DefOvl) %7BEAMER_ovl(Overlay) %4BEAMER_col(Col)
> #+OPTIONS: tags:nil
>
> #+BEAMER: \frame{\frametitle{Table of Contents}\tableofcontents}
>
>
> * Context
>
> ** Context
> This document is a minimal example, full of fake sentences:
> - the list of assets currently found, and
> - the things that *must*, /should/ or @could@ be developed in the
> coming
> months.
>
> Is "could" presented as an alert?
>
> Note that the previous slide, TOC, has a title, because I inserted
> it
> myself. When generated by Org, there is no frametitle.
>
>
> * Current assets
>
> ** DB
> *** Model
> **** Schema
> **** Partial X
> We extended X in order to put constraints on things (as one can
> with cardinalities).
> **** What
> *** Rules
> **** Other
> ***** First
> ***** Second
> ***** Rules, with link automatically made between rule failures and
> contributing properties
> **** Performance
> ***** Specialization of programs given partial data
> ***** Query reduction: optimize the queries so that with a minimal
> IO interaction the necessary data from a DB can be requested
> *** Computations
> **** Excel engine *IS NOT THE LAST ITEM*
> *** Integrity *has a subitem* (not shown by default)
> **** Seamless migrations is not visible if allowframebreaks is not set
>
> ** Workflow
> *** Petri net engine
> *** Workflow viewer
> *** Data mining
> *** Internal engine (based on new protocol)
> *** Semantic language (integration of the model and of the other
> stuff)
>
>
> * Future developments
> #+BEAMER: \frame[c]{\begin{center}Future developments\end{center}}
>
> ** Model
> *** Extensions (aggregation, negation)
> ** Workflow
> *** Workflow editor
>
>
> * COMMENT Setup
>
> # This is for the sake of Emacs.
> # Local Variables:
> # ispell-local-dictionary: "en_US"
> # End:
> --8<---------------cut here---------------end--------------->8---
>
> 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
- Carsten
next prev parent reply other threads:[~2010-01-06 10:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 9:46 New beamer support Sébastien Vauban
2010-01-06 10:06 ` Carsten Dominik [this message]
2010-01-06 10:59 ` Sébastien Vauban
2010-01-06 12:36 ` Carsten Dominik
2010-01-06 13:35 ` Sébastien Vauban
2010-01-06 14:23 ` Carsten Dominik
2010-01-06 14:31 ` Carsten Dominik
2010-01-06 15:35 ` Sébastien Vauban
2010-01-06 17:32 ` Carsten Dominik
2010-01-06 15:47 ` Sébastien Vauban
2010-01-06 17:34 ` Carsten Dominik
2010-01-07 9:38 ` Sébastien Vauban
2010-01-07 10:35 ` Carsten Dominik
2010-01-07 10:56 ` Sébastien Vauban
2010-01-06 11:13 ` Christian Lasarczyk
2010-01-06 11:57 ` Carsten Dominik
2010-01-06 13:06 ` Sébastien Vauban
2010-01-06 11:40 ` Eric S Fraga
2010-01-06 13:03 ` Sébastien Vauban
2010-01-06 13:25 ` Carsten Dominik
2010-01-06 16:22 ` Sébastien Vauban
2010-01-06 17:33 ` Carsten Dominik
2010-01-07 8:41 ` Sébastien Vauban
2010-01-07 14:39 ` Darlan Cavalcante Moreira
2010-01-07 15:43 ` Carsten Dominik
2010-01-07 16:16 ` Sébastien Vauban
2010-01-07 18:03 ` Darlan Cavalcante Moreira
2010-01-07 18:18 ` Carsten Dominik
2010-01-07 19:24 ` Sébastien Vauban
2010-01-07 16:48 ` Carsten Dominik
2010-01-07 8:54 ` Sébastien Vauban
2010-01-07 9:26 ` Carsten Dominik
2010-01-07 9:47 ` Sébastien Vauban
2010-01-07 10:00 ` Carsten Dominik
2010-01-07 10:21 ` Sébastien Vauban
2010-01-07 10:33 ` Carsten Dominik
2010-01-07 11:23 ` Sébastien Vauban
2010-01-07 11:30 ` [beamer] Order in preamble Sébastien Vauban
2010-01-07 13:15 ` Carsten Dominik
2010-01-07 15:54 ` Sébastien Vauban
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=4D2A7250-E096-4B8D-A7F0-85B043F01D08@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).