From: Nicolas Goaziou <n.goaziou@gmail.com>
To: jamshark70@dewdrop-world.net
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: New exporter, beamer confusion
Date: Tue, 05 Feb 2013 20:03:06 +0100 [thread overview]
Message-ID: <87fw1ashw5.fsf@gmail.com> (raw)
In-Reply-To: <CAFniQ7VRbOppQd3As9UEV+81ksY5b4dNBKVb_jLmUUxkyHa7gg@mail.gmail.com> (James Harkins's message of "Tue, 5 Feb 2013 17:01:30 +0800")
Hello,
> I'm attaching an org file that illustrates a couple of the beamer
> formatting options that I used a lot in the old exporter.
See below.
> 1. I *did* use the block environment to emphasize some text by pulling
> it out of the "itemize" bullet lists. If I customize blockenv in org
> to render as "itemize," then I lose the ability to do this (or, I have
> to call "block" something else).
>
> 2. BMCOL (column) layouts are completely ignored.
No. BMCOL are just different.
> 3. Strong *emphasis* now renders in red, instead of keeping the text's
> original color and switching to boldface.
Indeed. Strong emphasis in Beamer's jargon is \alert{...} (see Beamer
documentation about it). Letter are so large that \textbf{...} doesn't
fill the job well enough. I'm not saying that \textbf{...} is useless
(though I think it), but "alert" was preferred.
> I get the feeling here that the new beamer exporter was written
> without a lot of real-world user requirements.
FWIW, I have used it almost daily since I wrote it.
> Certainly, it's understandable that HTML, LaTeX article-style and ODT
> exporters would be more widely used and more important to get right
> first. For beamer, though, I can't reconcile the announcement ("Even
> though the internals are completely different, the new exporter mostly
> behaves like its predecessor. There are only a few noticeable
> changes") with the fact that the new beamer exporter is a rather
> different animal that completely breaks compatibility with org files
> written for the old exporter, and may actually require a complete redo
> of the org markup for each file.
You are half correct. I admit: I forgot to mention that Beamer back-end
was a bit different from its predecessor. Though, it doesn't require
a complete redo, there's just some work to do at the headline level.
> I know my emacs-lisp chops are not up to the task of fixing what is
> broken in the new beamer exporter.
Nothing is broken in it (at least AFAIK). There are just some changes to
do.
> I can supply a couple dozen source
> files, to help decide what level of backward compatibility is
> feasible. I'm not sure how else I can help.
Let's start slowly. I think you can get how to make the changes yourself
with a couple of examples. Since you seem to like lists (you know that
Till Tantau frowns upon the use of third level lists in presentations,
don't you?), the first rule to know is:
Headlines will never, ever, become lists in the new Beamer back-end.
If you want lists, use lists. There's a handy command to do that change:
mark the subtree you want to change, and use "C-c -".
New back-end is more block friendly than lists friendly.
> At least, it would be good to clarify, with respect to the
> announcement, if the new beamer exporter is intended to be reasonably
> backward-compatible with the old (with not-too-intrusive tweaks).
It all depends on what you mean by reasonably. You can obtain the same
output, but there are changes to make in Org files.
> If that was the intent, then it's not ready for release. Otherwise,
> I'd be happy to help draw up an upgrade path for people like myself
> who have developed workflows for the old exporter that will eventually
> not be supported anymore.
Thank you. I'll try to help you get started. You might even come to like
the new back-end in the process.
> In the meantime, I must stick with the old exporter, though I'll keep
> the discussion alive to hash out on the mailing list what needs to be
> done to make the new one production-ready for me.
Fair enough.
I'm attaching an updated version of your simple document. Besides moving
subtree to lists, there only other change was at the columns level.
If you use a headline with only a BEAMER_col property, its title will be
ignored and can be used as a container. If you provide it an additional
environment (like block), the new environment will be put in the column
and will fill it. Moreove, the :BEAMER_col: property requires a decimal
number as value, not a length.
Oh, yes, and BEAMER_FRAME_LEVEL doesn't exist anymore. It's H:... in the
OPTIONS line.
#+begin_src org
#+LANGUAGE: en
#+OPTIONS: H:2 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
#+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc
#+startup: beamer
#+LaTeX_CLASS: beamer
#+LaTeX_CLASS_OPTIONS: [presentation]
#+BEAMER_THEME: default
#+COLUMNS: %45ITEM %10BEAMER_env(Env) %10BEAMER_act(Act) %4BEAMER_col(Col) %8BEAMER_opt(Opt)
#+PROPERTY: BEAMER_col_ALL 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 0.0 :ETC
#+TITLE: Testing new beamer exporter
#+AUTHOR: H. James Harkins
#+EMAIL: jamshark70@yaddayadda.com
#+DATE: 7 November 2012
#+BEGIN_LaTeX
\AtBeginSection[] % Do nothing for \section*
{
\begin{frame}<beamer>
\frametitle{Outline}
\tableofcontents[currentsection]
\end{frame}
}
#+END_LaTeX
* Section A
** Slide 1
- Third-level
- Fourth-level
** Ancient history: *Music \emph{n}* languages
- Early pioneers at *Bell Labs* in New Jersey
- Max Mathews, Jean-Claude Risset, John Chowning
- They could make the digital tapes, but not play them
- Drove the tapes up to Columbia University (NYC)
- ... just to find out that it didn't work
- Mainframe, batch processing
- Prepare /instrument/ and /score/ files
- Run the program
- An audio file comes out... hours later
- Modern version: *csound*
- Modern CPUs can render faster than real-time
#+BEAMER: \pause{}
*** *Without these early researchers, there is no Cubase, no Logic... nothing.*
** SuperCollider live
- Map /processes/ onto MIDI keys
- /Driver processes/ for complex transitions
- Map /global controls/ to MIDI controllers
- Synthesis parameters (filters, etc.)
- Composition parameters (rhythmic activity, probabilities etc.)
*** Left column (title ignored) :BMCOL:
:PROPERTIES:
:BEAMER_col: 0.3
:END:
- This is my own design
- SC has no standard GUI!
- You decide what /you/ need
*** Right column (title ignored) :BMCOL:
:PROPERTIES:
:BEAMER_col: 0.7
:END:
- GUI
#+ATTR_LaTeX: :options "width=6.5cm"
[[ /media/39ED-A99A/cubase/2012audio/10-intro-sc/img/controlpanel.pdf]]
#+end_src
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-02-05 19:03 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 16:37 org-url-hexify-p is not respected James Harkins
2012-09-10 1:50 ` James Harkins
2012-09-10 4:58 ` Nick Dokos
2012-09-10 6:16 ` James Harkins
2012-09-10 6:37 ` Jambunathan K
2012-09-10 6:48 ` James Harkins
2012-09-10 7:12 ` Jambunathan K
[not found] ` <CAFniQ7W_5QMUawD2NObyhy2_Y647as-NthobZ9OgAX4NLcVJBw@mail.gmail.com>
2012-09-11 10:22 ` James Harkins
2012-09-11 13:10 ` Activating modules before org-install (was: org-url-hexify-p is not respected) Memnon Anon
2012-09-11 13:56 ` Jonathan Leech-Pepin
2012-09-11 17:06 ` org-url-hexify-p is not respected Charles Philip Chan
2012-09-23 10:05 ` Bastien
2012-09-26 17:59 ` Michael Brand
2012-09-26 21:50 ` Bastien
2012-09-27 6:18 ` Michael Brand
[not found] ` <jamshark70@gmail.com>
2012-08-12 2:55 ` MobileOrg, webdav, correct use of org-mobile-directory? James Harkins
2012-08-12 4:29 ` Nick Dokos
2012-08-12 7:12 ` James Harkins
2012-08-12 8:43 ` Bastien
2012-08-12 8:50 ` James Harkins
2012-08-12 13:11 ` Nick Dokos
2012-08-18 23:25 ` Adam Spiers
2012-08-19 1:35 ` Adam Spiers
2012-08-19 5:49 ` James Harkins
2012-08-20 20:03 ` Rémi Vanicat
2012-08-19 2:41 ` Nick Dokos
2012-08-12 11:38 ` James Harkins
2012-08-12 12:40 ` Nick Dokos
2012-08-12 13:12 ` Nick Dokos
2012-09-29 16:34 ` LaTeX beamer export: relative file links? Nick Dokos
2012-09-30 2:04 ` James Harkins
2013-01-10 3:40 ` <M-S-left/right> changed? Nick Dokos
2013-01-10 9:17 ` James Harkins
2013-02-05 7:21 ` New exporter, beamer confusion Nick Dokos
2013-02-05 9:01 ` James Harkins
2013-02-05 13:20 ` Sebastien Vauban
2013-02-05 13:55 ` Nick Dokos
2013-02-05 19:03 ` Nicolas Goaziou [this message]
2013-02-06 0:11 ` Eric S Fraga
2013-02-06 18:55 ` Nicolas Goaziou
2013-02-06 22:39 ` Eric S Fraga
2013-02-07 12:31 ` Nicolas Goaziou
[not found] ` <37646106030B4CA98C6A7717FBD89D50@gmail.com>
[not found] ` <87vca4jigj.fsf@gmail.com>
2013-02-07 14:49 ` Vincent Beffara
2013-02-07 14:58 ` Nicolas Goaziou
2013-02-07 17:08 ` Rasmus
2013-02-07 21:48 ` Nicolas Goaziou
2013-02-07 23:38 ` Rasmus
2013-02-08 21:41 ` Nicolas Goaziou
2013-02-08 13:40 ` Eric S Fraga
2013-02-06 2:12 ` James Harkins
2013-02-06 4:35 ` Eric S Fraga
2013-02-06 12:32 ` Rasmus
2013-02-06 13:12 ` Suvayu Ali
2013-02-06 13:45 ` Sebastien Vauban
2013-02-06 19:57 ` Nicolas Goaziou
2013-02-07 1:32 ` James Harkins
2013-02-05 9:36 ` Eric S Fraga
2013-02-25 6:25 ` How to make the new exporter open PDF using evince? James Harkins
2013-02-25 7:01 ` Mike Gauland
2013-02-25 6:52 ` Nick Dokos
2013-02-25 13:06 ` James Harkins
2013-02-26 2:40 ` Martin Marier
2013-02-27 9:51 ` James Harkins
[not found] <CAFniQ7UgwaQ5jO2r7iJ7PbakWfpvsJGZw2FNNf+sawwvKqSUqQ@mail.gmail.com>
2012-09-29 5:55 ` LaTeX beamer export: relative file links? James Harkins
-- strict thread matches above, loose matches on Subject: below --
2013-01-10 2:38 <M-S-left/right> changed? James Harkins
2013-02-04 4:00 New exporter, beamer confusion James Harkins
2013-02-04 6:39 ` Suvayu Ali
2013-02-04 8:55 ` James Harkins
2013-02-04 19:51 ` Nicolas Goaziou
2013-02-05 0:09 ` James Harkins
2013-02-05 12:32 ` Eric S Fraga
2013-02-05 18:06 ` Nicolas Goaziou
2013-02-05 23:49 ` Eric S Fraga
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=87fw1ashw5.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
--cc=nicholas.dokos@hp.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).