Re: [Orgmode] Re: Beamer support in Org-mode
On Nov 27, 2009, at 9:15 AM, Eric S Fraga wrote:
At Thu, 26 Nov 2009 15:47:53 -0600,
Russell Adams wrote:
On Thu, Nov 26, 2009 at 10:38:20PM +0100, S??bastien Vauban wrote:
I just know ('ve seen it) that Russell Adams (hep!??;-)) uses
Prosper, one of
the old alternatives, before Beamer came on the "market". Maybe he
could tell
us some interesting things about this planned construction?
I heard my name *ears burning*.
I just made my first Beamer presentation in Org recently, and I'm
*sold* on it.
http://www.adamsinfoserv.com/AISTWiki/pub/AIS/Presentations/HoustonAIXUsersGroup_ToolsTipsTricks.pdf
On this note, the slides I was preparing and which in some sense
motivated this whole org to beamer debate can be found here
temporarily:
http://www.homepages.ucl.ac.uk/~ucecesf/tmp/heatandpipes.pdf
See particularly slide 100 for the type of slide I would like to be
able to handle easily in org mode, if at all possible.
Hi Eric,
here is how I would make your slide 100 with the new setup. There are
different ways to do it - for illustration I have made your legend a
block environment with title "Legend".
* Typical configuration
** Graphics :B_ignoreheading:
:PROPERTIES:
:BEAMER_env: ignoreheading
:BEAMER_col: 0.5
:END:
[[./blue.png]]
** Legend :B_block:
:PROPERTIES:
:BEAMER_env: block
:BEAMER_col: 0.5
:END:
- $P_1$, pressure at the tank liquid surface
- $h_1$, height of the liquid surface above the pump centre-line at
the suction inlet
- $u_1$, liquid velocity on the surface
- $u_2$, velocity at the pump inlet
- $h_\mathrm{f}$, total piping friction loss between (1) and (2)
___
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
[Orgmode] Re: Beamer support in Org-mode
Hi Carsten
I've been using org-mode to create a few presentations and found it to
be extremely productive. I use different levels for parts (in the past),
sections and subsections. Beyond that I just use lists. I haven't used
blocks and columns (probably because it wasn't easily possible so far).
Also I use separate org files for all presentations.
See
http://www.daisy2009.de/files/presentations/itc/egli__daisy_producer.pdf,
http://liblouis.googlecode.com/files/liblouisSlides.pdf and
http://liblouis.googlecode.com/files/liblouisSlides.org for examples
Here's the relevant expert from my .emacs
'(org-export-latex-classes (quote (("beamer" "\\documentclass[]{beamer}
\\usetheme{Frankfurt}
\\usepackage{multimedia}
\\usepackage[english]{babel}
\\usepackage[utf8]{inputenc}
\\usepackage{hyperref}" ("\\section{%s}" . "\\section{%s}") ("\\subsection{%s}"
. "\\subsection{%s}") ("\\begin{frame}{%s}" "\\end{frame}" "\\begin{frame}{%s}"
"\\end{frame}")
Carsten Dominik writes:
> 1. Don't automatically use a specific headline level to create the
> columns
>environment - at least make that configurable.
Generally I like the idea of using the levels as an indication for
beamer. However this needs to be configurable, as I have also used parts
in the past for example.
> 2. Make beamer export force org-export-headline-levels equal org-
> beamer-frame-level,
>so that headlines below the frame level automatically become itemize
>levels, unless modified by tags or properties.
I don't really care about that too much (in fact I think it just
introduces confusion). I just always used lists for bullet points.
> 3. Use meta data to make headlines special, instead of mixing this
>stuff into the. I first thought this is too hard - but maybe it is
>OK when edited with column view? Hmm, I am only half-sold on this
> - properties
>are so hard to see when you need them frequently during editing.
This sounds reasonable, as I usually create an outline of the ideas
first and from that create a presentation. Later I might reuse it for a
paper, so I don't really want it to be interspersed with layout
information.
> Thomas asked for the possibility to export a subtree as a
> presentation, with *relative* levels determining functionality. This
> should be easy - when selection a subtree with `C-c @' and then
> exporting,
> relative levels are already being used now, for any kind of export.
I don't have a need for that as I use separate files for each
presentation.
Another thing that I tried to use was alerts (and colors) in bullet
points. I seem to remember that it didn't work. I should try again. It
appears that Eric managed to get them to work.
Thanks
Christian
___
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
Re: [Orgmode] Re: Beamer support in Org-mode
At Fri, 27 Nov 2009 14:48:58 +0100, Carsten Dominik wrote: > > > On Nov 27, 2009, at 10:09 AM, Sébastien Vauban wrote: > > > Hi all, > > > > Eric S Fraga wrote: > >> one thing that would be useful (and which I've mentioned in a reply > >> to Dan) > >> is the ability to specify options for the documentclass (e.g. bigger, > >> handout). This would actually be useful in normal latex export as > >> well, of > >> course. > > > > Yes, we (would) need such a feature. For example, in our company > > LaTeX class, > > we have options like `black' for uncolored output, or `acro' for > > putting > > automatically an acronym sections. There are others as well. > > You can now use > > #+LaTeX_CLASS_OPTIONS: [black] > > and also a property if you are exporting a specific subtree. Excellent! I now have my three beamer classes (bigger, smaller, handout) down to one. Much easier to manage. Thanks, eric ___ 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
S5 Slideschows / Presentations - was Re: [Orgmode] Re: Beamer support in Org-mode
Dan Davison writes: > Magnus Henoch writes: > >> Dan Davison writes: >> >>> And it's possible to create something like a slide-show in HTML/CSS -- >>> although I never see anyone doing it. >> >> Have a look at S5: http://meyerweb.com/eric/tools/s5/s5-intro.html > > Thankyou, that looks really nice. It would be great for org to be able > to target an XHTML-based slide format like this in addition to beamer, > wouldn't it? It would require some work, but the XHTML structure below > seems encouragingly straightforward. Perhaps a relatively effortless > starting point would be dividing some of the new variables controlling > beamer export into general-presentation and beamer-specific sets > (e.g. the location of the slide and slide components in a subtree; I > know, I already said this...) > > I'm pasting some relevant information from the Wikipedia entry below in > case anyone more knowledgable about org (X)HTML/XOXO export has any > thoughts. > > Dan > >>From wikipedia: > > --- > S5 (Simple Standards-Based Slide Show System) is an XHTML-based file > format for defining slideshows. It was created by Eric Meyer as an > alternative to the browser-centric Opera Show Format. S5 is not a > presentation program, but fulfills the same purpose in combination with > a standards-compliant web browser. > > The text of an S5 presentation can be stored in a single XHTML > file. This file contains several slides which are coded in the following > way. > > > slide title > >the first point >the second point >the third point > > > ... additional material that appears > on the handout > > I'd suggest, to use XSLT to achive this. It's reliable, fast and a good thing to learn if you want to transform current export. 2.) I'd suggest to use a different thread?? Sebastian ___ 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
Re: [Orgmode] Re: Beamer support in Org-mode
Magnus Henoch writes: > Dan Davison writes: > >> And it's possible to create something like a slide-show in HTML/CSS -- >> although I never see anyone doing it. > > Have a look at S5: http://meyerweb.com/eric/tools/s5/s5-intro.html Thankyou, that looks really nice. It would be great for org to be able to target an XHTML-based slide format like this in addition to beamer, wouldn't it? It would require some work, but the XHTML structure below seems encouragingly straightforward. Perhaps a relatively effortless starting point would be dividing some of the new variables controlling beamer export into general-presentation and beamer-specific sets (e.g. the location of the slide and slide components in a subtree; I know, I already said this...) I'm pasting some relevant information from the Wikipedia entry below in case anyone more knowledgable about org (X)HTML/XOXO export has any thoughts. Dan >From wikipedia: --- S5 (Simple Standards-Based Slide Show System) is an XHTML-based file format for defining slideshows. It was created by Eric Meyer as an alternative to the browser-centric Opera Show Format. S5 is not a presentation program, but fulfills the same purpose in combination with a standards-compliant web browser. The text of an S5 presentation can be stored in a single XHTML file. This file contains several slides which are coded in the following way. slide title the first point the second point the third point ... additional material that appears on the handout S5 presentations can be viewed in outline and slideshow mode – Cascading Style Sheets (CSS) are used to define different layouts for outline, slideshow and print. Navigation controls, a dynamically generated list of slides and accesskeys allow browsing back and forth. A more semantic version of the S5 format is based on the XOXO microformat and uses instead of divs for the slides, as well as instead of a div for the overall presentation. --- > > Magnus > > > > ___ > 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 ___ 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
[Orgmode] Re: Beamer support in Org-mode
Hi Carsten, Carsten Dominik wrote: > On Nov 27, 2009, at 10:09 AM, Sébastien Vauban wrote: >> Eric S Fraga wrote: >>> one thing that would be useful (and which I've mentioned in a reply to >>> Dan) is the ability to specify options for the documentclass (e.g. bigger, >>> handout). This would actually be useful in normal latex export as well, of >>> course. >> >> Yes, we (would) need such a feature. For example, in our company LaTeX >> class, we have options like `black' for uncolored output, or `acro' for >> putting automatically an acronym sections. There are others as well. > > You can now use > > #+LaTeX_CLASS_OPTIONS: [black] > > and also a property if you are exporting a specific subtree. Thanks a lot. 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
[Orgmode] Re: Beamer support in Org-mode
Dan Davison writes: > And it's possible to create something like a slide-show in HTML/CSS -- > although I never see anyone doing it. Have a look at S5: http://meyerweb.com/eric/tools/s5/s5-intro.html Magnus ___ 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
Re: [Orgmode] Re: Beamer support in Org-mode
On Nov 27, 2009, at 10:09 AM, Sébastien Vauban wrote: Hi all, Eric S Fraga wrote: one thing that would be useful (and which I've mentioned in a reply to Dan) is the ability to specify options for the documentclass (e.g. bigger, handout). This would actually be useful in normal latex export as well, of course. Yes, we (would) need such a feature. For example, in our company LaTeX class, we have options like `black' for uncolored output, or `acro' for putting automatically an acronym sections. There are others as well. You can now use #+LaTeX_CLASS_OPTIONS: [black] and also a property if you are exporting a specific subtree. - Carsten ___ 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
[Orgmode] Re: Beamer support in Org-mode
Hi Carsten, Carsten Dominik wrote: > On Nov 26, 2009, at 7:40 PM, Dan wrote: >> Also, I do agree with others that to the extent possible we want >> presentations to emerge naturally out of 'normal' org-files with the help >> of established org mechanisms such as selective subtree export. E.g. using >> the heading title to set the column width feels wrong; the natural reaction >> is to think that that sort of metadata should be in a property. > > OK, I hear you all pull the same string, that Org-mode files should be > beamer presentations as they are, more or less. > > Here are some ideas in that direction: > > 1. Don't automatically use a specific headline level to create the columns >environment - at least make that configurable. > > 2. Make beamer export force org-export-headline-levels equal >org-beamer-frame-level, so that headlines below the frame level >automatically become itemize levels, unless modified by tags or >properties. > > 3. Use meta data to make headlines special, instead of mixing this stuff >into the. I first thought this is too hard - but maybe it is OK when >edited with column view? Hmm, I am only half-sold on this - properties >are so hard to see when you need them frequently during editing. > > Thomas asked for the possibility to export a subtree as a presentation, with > *relative* levels determining functionality. This should be easy - when > selection a subtree with `C-c @' and then exporting, relative levels are > already being used now, for any kind of export. As far as I understand, I perfectly agree with the explained approach, yes! Thanks for all, 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
[Orgmode] Re: Beamer support in Org-mode
Hi all, Eric S Fraga wrote: > one thing that would be useful (and which I've mentioned in a reply to Dan) > is the ability to specify options for the documentclass (e.g. bigger, > handout). This would actually be useful in normal latex export as well, of > course. Yes, we (would) need such a feature. For example, in our company LaTeX class, we have options like `black' for uncolored output, or `acro' for putting automatically an acronym sections. There are others as well. The number of combinations can explode quite quickly, so that the smart workaround of Eric is not usable outside of `beamer' and `beamerhandout'. 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
Re: [Orgmode] Re: Beamer support in Org-mode
At Thu, 26 Nov 2009 15:47:53 -0600,
Russell Adams wrote:
>
> On Thu, Nov 26, 2009 at 10:38:20PM +0100, S??bastien Vauban wrote:
> > I just know ('ve seen it) that Russell Adams (hep!??;-)) uses Prosper, one
> > of
> > the old alternatives, before Beamer came on the "market". Maybe he could
> > tell
> > us some interesting things about this planned construction?
>
> I heard my name *ears burning*.
>
> I just made my first Beamer presentation in Org recently, and I'm
> *sold* on it.
>
> http://www.adamsinfoserv.com/AISTWiki/pub/AIS/Presentations/HoustonAIXUsersGroup_ToolsTipsTricks.pdf
On this note, the slides I was preparing and which in some sense
motivated this whole org to beamer debate can be found here
temporarily:
http://www.homepages.ucl.ac.uk/~ucecesf/tmp/heatandpipes.pdf
See particularly slide 100 for the type of slide I would like to be
able to handle easily in org mode, if at all possible.
> > > Also, I do agree with others that to the extent possible we want
> > > presentations to emerge naturally out of 'normal' org-files
> >
> > Yes, I do have the same concern. An Org file for Beamer or a standard Org
> > file
> > should have almost no differences -- except for the class. I think it's even
> > possible for small and standard slides show that there would be no
> > difference
> > at all, except once again the length of sentence and the numerous headlines.
>
> I think any Beamer enhancements should be encoded in the headline
> properties (section, transition, etc). Don't introduce new syntax,
> make it work out of the box with reasonable defaults, and then allow
> customization via property drawers for individual headlines, and the
> export options header for global options.
I agree with you. What I've done so far is leverage the current
capabilities of org without requiring any changes. All of my slides
were generated by my adding my own interpretation of level 3+
headlines, an interpretation that is indeed beamer specific. This is
probably not ideal but it worked!
However, I must admit that I'm not too bothered about having a
specific interpretation of headlines in my case because I don't mix
presentations with other org content. My talks are always standalone
files. Nevertheless, I know others work differently and I'm sure I
can imagine cases where I would like to have a small set of slides
embedded within a larger org files.
___
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
Re: [Orgmode] Re: Beamer support in Org-mode
On Thu, Nov 26, 2009 at 10:38:20PM +0100, S??bastien Vauban wrote:
> I just know ('ve seen it) that Russell Adams (hep!??;-)) uses Prosper, one of
> the old alternatives, before Beamer came on the "market". Maybe he could tell
> us some interesting things about this planned construction?
I heard my name *ears burning*.
I just made my first Beamer presentation in Org recently, and I'm
*sold* on it.
http://www.adamsinfoserv.com/AISTWiki/pub/AIS/Presentations/HoustonAIXUsersGroup_ToolsTipsTricks.pdf
> > Also, I do agree with others that to the extent possible we want
> > presentations to emerge naturally out of 'normal' org-files
>
> Yes, I do have the same concern. An Org file for Beamer or a standard Org file
> should have almost no differences -- except for the class. I think it's even
> possible for small and standard slides show that there would be no difference
> at all, except once again the length of sentence and the numerous headlines.
I think any Beamer enhancements should be encoded in the headline
properties (section, transition, etc). Don't introduce new syntax,
make it work out of the box with reasonable defaults, and then allow
customization via property drawers for individual headlines, and the
export options header for global options.
--
Russell Adamsrlad...@adamsinfoserv.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
___
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
[Orgmode] Re: Beamer support in Org-mode
Dan Davison wrote:
>> On Nov 26, 2009, at 1:17 AM, Carsten Dominik wrote:
>>> NOW is the time to chime in.
>
> I don't know if this is helpful from someone who hasn't thought through the
> details of beamer support but just in case: is there any chance that we
> should be thinking at this stage of a generic org-presentation API which
> would initially support just beamer but which would leave open the
> possibility for others to implement other slide presentation engines? For
> example I remember that someone once brought up the possibility on this list
> of exporting org to OpenOffice presentation format. And it's possible to
> create something like a slide-show in HTML/CSS -- although I never see
> anyone doing it. There are at least some things in common between different
> slide-show engines, such as where to break from slide to slide, slide
> titles, non-slide notes, etc.
I have absolutely no experience with other "slide" engines in LaTeX. But I
think (as well) it's a good time to think at commonalities between these, so
that one extract the right model, even if we only support Beamer (which I
think is the best) in the first place, and maybe for ever. But it would maybe
ensure we ask ourselves the right questions.
I just know ('ve seen it) that Russell Adams (hep! ;-)) uses Prosper, one of
the old alternatives, before Beamer came on the "market". Maybe he could tell
us some interesting things about this planned construction?
> Also, I do agree with others that to the extent possible we want
> presentations to emerge naturally out of 'normal' org-files
Yes, I do have the same concern. An Org file for Beamer or a standard Org file
should have almost no differences -- except for the class. I think it's even
possible for small and standard slides show that there would be no difference
at all, except once again the length of sentence and the numerous headlines.
At least, the Beamer Org file would be the first mind map, or the skeleton, of
a real-document, would it outgrow from slides to document.
> with the help of established org mechanisms such as selective subtree
> export. E.g. using the heading title to set the column width feels wrong;
> the natural reaction is to think that that sort of metadata should be in a
> property.
I don't know which exact representation it should have, but I'm puzzled by
headlines setting the width of columns, too.
Best regards,
Fabrice Niessen
--
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
[Orgmode] Re: Beamer support in Org-mode
Christoph Groth wrote: > Nice idea to create LaTeX-presentations using orgmode. Though, whenever > using beamer, I always find myself having to tweak some spaces on a > fairly low level. I'm curious whether it will work out to create > non-trivial presentations by using orgmode only. I am sure we will make it! >> If the frame title contains the string "\\", the line will be split at >> that location, and the second half become the frame /subtitle/. > > Sometimes one might have a frame title which is too wide for one line. > Then one might want to split the title at a specific place -- and that > is done by inserting a \\ there. An alternative would be for you to use \linebreak in such cases (when you wanna break the line because it's too long). 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
[Orgmode] Re: Beamer support in Org-mode
Hi Carsten,
Carsten Dominik wrote:
> On Nov 26, 2009, at 3:01 PM, Sébastien Vauban wrote:
>> Carsten Dominik wrote:
>>> [...] before I polish I would like comments on this outline.
>>>
>>> 1 Organization
>>> ~~~
>>>
>>> 1.1 Sections
>>> =
>>>
>>> By default, level one headlines become sections in the beamer
>>> document. You can configure the variable org-beamer-frame-level
>>> to change this. Setting it to three will make level 2 headlines
>>> become subsections. For the rest of this document, I will assume
>>> that this variable has its default value 2.
>>
>> I was used to use Org level-1 headlines as the frame title... but I've never
>> resolved how to put sections in my beamer slides (via Org) -- though this
>> was
>> not that important yet for me, as I only converted slides made by others in
>> PowerPoint, and they don't have such sections (and TOC visible in the left
>> bar).
>>
>> Though, I find this way of structuring excellent: sound and logical. Plus it
>> is even customizable. What else would we want? Nothing...
>>
>>
>>> 1.3 Columns
>>>
>>> Headlines one below frames (level 3 by default) can be used start
>>> columns on a frame. The presence of such a headline without a
>>> beamer tag (see below) will create the columns environment. The
>>> text in the headline is ignored. It is helpful to write
>>> "columns" in this headline anyway.
>>
>> Would *I* be asked about my true opinion, I would really object against this
>> one... Except that you say "can be used". So, I guess we're not forced.
>
> Of course *you* are asked.
>
> I am wondering: What function do the headlines in your document
> under the frame level have? How do you export them? I guess
> you can't have them spit out subsection or so. What you your
> class configuration?
That's what I tried to say above:
>> I was used to use Org level-1 headlines as the frame title... but I've
>> never resolved how to put sections in my beamer slides (via Org).
I currently couldn't have sections in my beamer presentation.
- The level-1 headlines are the frame titles.
- The level-2 headlines are the level-1 items of the slides.
My current configuration:
--8<---cut here---start->8---
(add-to-list 'org-export-latex-classes
'("beamer"
"\\documentclass[t]{beamer}
\\mode<{{{beamermode}}}>
{
\\usethemebeamertheme
}
\\usepackage[english]{babel}
\\usepackage[utf8x]{inputenc}
\\usepackage{times}
\\usepackage[T1]{fontenc}
\\usepackage{pgf}
\\institutebeamerinstitute
\\subjectbeamersubject"
("\\begin{frame}\\frametitle{%s}\\begin{itemize}"
"\\end{itemize}\\end{frame}"
"\\begin{frame}\\frametitle{%s}\\begin{itemize}"
"\\end{itemize}\\end{frame}")
("\\item{%s}" . "\\item*{%s}")))
--8<---cut here---end--->8---
>> My main "problem" here is that I like the idea of being to convert back or
>> forward between Org documents and Org-beamer documents. Such headlines would
>> not mean anything for a "normal" Org document, as you already pointed out.
>>
>> Now, if this is not the default interpretation, it could be OK for
>> everybody.
>> We should show this in the example below:
>> - normal level-3 headlines (level-1 for Beamer) and
>> - "column" level-3 headlines.
>
> Yes, this would be useful. Indeed, we should work on an extensive example
> once we have settled for a structure/format. Which is not yet the case.
I'll try to help on that, as much as I can.
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
[Orgmode] Re: Beamer support in Org-mode
Nice idea to create LaTeX-presentations using orgmode. Though, whenever
using beamer, I always find myself having to tweak some spaces on a
fairly low level. I'm curious whether it will work out to create
non-trivial presentations by using orgmode only.
Carsten Dominik writes:
> If the frame title contains the string "\\", the line will be split at
> that location, and the second half become the frame /subtitle/.
Sometimes one might have a frame title which is too wide for one line.
Then one might want to split the title at a specific place -- and that
is done by inserting a \\ there. Therefore, I suggest to use some other
magic string. What about an unquoted ampersand ("&")? This character is
already used in LaTeX to split things and its unquoted use in a
frame title is actually an error.
Christoph
___
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
Re: [Orgmode] Re: Beamer support in Org-mode
Hi Sebastian, On Nov 26, 2009, at 3:01 PM, Sébastien Vauban wrote: Hi Carsten, Carsten Dominik wrote: [...] before I polish I would like comments on this outline. 1 Organization ~~~ 1.1 Sections = By default, level one headlines become sections in the beamer document. You can configure the variable org-beamer-frame-level to change this. Setting it to three will make level 2 headlines become subsections. For the rest of this document, I will assume that this variable has its default value 2. I was used to use Org level-1 headlines as the frame title... but I've never resolved how to put sections in my beamer slides (via Org) -- though this was not that important yet for me, as I only converted slides made by others in PowerPoint, and they don't have such sections (and TOC visible in the left bar). Though, I find this way of structuring excellent: sound and logical. Plus it is even customizable. What else would we want? Nothing... 1.2 Frames === Level 2 headline (or the level configured in org-beamer-frame-level) become frames. The headline text become the frame title, but if no headline text is given, the frame gets no title. If the frame title contains the string "\\", the line will be split at that location, and the second half become the frame /subtitle/. Excellent. Really. 1.3 Columns Headlines one below frames (level 3 by default) can be used start columns on a frame. The presence of such a headline without a beamer tag (see below) will create the columns environment. The text in the headline is ignored. It is helpful to write "columns" in this headline anyway. Would *I* be asked about my true opinion, I would really object against this one... Except that you say "can be used". So, I guess we're not forced. Of course *you* are asked. I am wondering: What function do the headlines in your document under the frame level have? How do you export them? I guess you can't have them spit out subsection or so. What you your class configuration? My main "problem" here is that I like the idea of being to convert back or forward between Org documents and Org-beamer documents. Such headlines would not mean anything for a "normal" Org document, as you already pointed out. Now, if this is not the default interpretation, it could be OK for everybody. We should show this in the example below: - normal level-3 headlines (level-1 for Beamer) and - "column" level-3 headlines. Yes, this would be useful. Indeed, we should work on an extensive example once we have settled for a structure/format. Which is not yet the case. - Carsten 1.4 A column = Headlines below a columns environment (level 4 by default) open a column. The text in the headline should be a number smaller than one and will be used to define the column width. 1.5 Block-like environments Any headline can become a block-like environment by tagging it with a beamer tag. For examples, `:B_block:' will trigger the creation of a block environment, while `:B_theorem:' will trigger the creation of a theorem environment. When it makes sense, the headline text is used in an appropriate argument of the environment, if that does not make sense, it is ignored. 1.6 Overlay/action tag and environment options === Any headline can contain three types of cookies `<...>': The overlay/action setting for the environment `[<...>]': The default overlay/action specification for the content of the environment, which can be overwritten locally by each content element. `[...]': Optional argument(s) for the environment These can be given in arbitrary order freely in the headline. Org-mode will fish them out and insert them in the appropriate locations in the \begin statement of the environment. I never really used overlays yet (only to play with). Though, this seems nice to me, even if... Having these cookies plainly in the headline reduces the usability of the document as a normal document. I have been thinking to move them into comments or properties, but I think this is, in the end, less convenient. I people want to export these in other ways as well, we can write a function to clean up 1.7 Overlay/action in list environment === For plain list environments (ordered, unordered, and description lists) you can start each item optionally with an overlay specification `<...>'. If any item in the list contains a default specification `[<...>]', this will be moved into the begin statement of the itemize/enumerate/description environment, to provide a default setting for the list items. 1.8 Embedded LaTeX === As is normal for Org-mode, you can embed LaTeX commands into the text, and they will be transferred literally into the exported document. In particular, you can also embed beamer-specific comman
[Orgmode] Re: Beamer support in Org-mode
Hi Carsten, Carsten Dominik wrote: > [...] before I polish I would like comments on this outline. > > 1 Organization > ~~~ > > 1.1 Sections > = > > By default, level one headlines become sections in the beamer > document. You can configure the variable org-beamer-frame-level > to change this. Setting it to three will make level 2 headlines > become subsections. For the rest of this document, I will assume > that this variable has its default value 2. I was used to use Org level-1 headlines as the frame title... but I've never resolved how to put sections in my beamer slides (via Org) -- though this was not that important yet for me, as I only converted slides made by others in PowerPoint, and they don't have such sections (and TOC visible in the left bar). Though, I find this way of structuring excellent: sound and logical. Plus it is even customizable. What else would we want? Nothing... > 1.2 Frames > === > Level 2 headline (or the level configured in > org-beamer-frame-level) become frames. The headline text become > the frame title, but if no headline text is given, the frame gets > no title. If the frame title contains the string "\\", the line > will be split at that location, and the second half become the > frame /subtitle/. Excellent. Really. > 1.3 Columns > > Headlines one below frames (level 3 by default) can be used start > columns on a frame. The presence of such a headline without a > beamer tag (see below) will create the columns environment. The > text in the headline is ignored. It is helpful to write > "columns" in this headline anyway. Would *I* be asked about my true opinion, I would really object against this one... Except that you say "can be used". So, I guess we're not forced. My main "problem" here is that I like the idea of being to convert back or forward between Org documents and Org-beamer documents. Such headlines would not mean anything for a "normal" Org document, as you already pointed out. Now, if this is not the default interpretation, it could be OK for everybody. We should show this in the example below: - normal level-3 headlines (level-1 for Beamer) and - "column" level-3 headlines. > 1.4 A column > = > Headlines below a columns environment (level 4 by default) open a > column. The text in the headline should be a number smaller than > one and will be used to define the column width. > > 1.5 Block-like environments > > Any headline can become a block-like environment by tagging it > with a beamer tag. For examples, `:B_block:' will trigger the > creation of a block environment, while `:B_theorem:' will trigger > the creation of a theorem environment. When it makes sense, the > headline text is used in an appropriate argument of the > environment, if that does not make sense, it is ignored. > > 1.6 Overlay/action tag and environment options > === > Any headline can contain three types of cookies > > `<...>': The overlay/action setting for the environment > `[<...>]': The default overlay/action specification for the > content of the environment, which can be overwritten locally > by each content element. > `[...]': Optional argument(s) for the environment > > These can be given in arbitrary order freely in the headline. > Org-mode will fish them out and insert them in the appropriate > locations in the \begin statement of the environment. I never really used overlays yet (only to play with). Though, this seems nice to me, even if... > Having these cookies plainly in the headline reduces the > usability of the document as a normal document. I have been > thinking to move them into comments or properties, but I think > this is, in the end, less convenient. I people want to export > these in other ways as well, we can write a function to clean > up > > 1.7 Overlay/action in list environment > === > For plain list environments (ordered, unordered, and description > lists) you can start each item optionally with an overlay > specification `<...>'. If any item in the list contains a > default specification `[<...>]', this will be moved into the > begin statement of the itemize/enumerate/description environment, > to provide a default setting for the list items. > > 1.8 Embedded LaTeX > === > As is normal for Org-mode, you can embed LaTeX commands into the > text, and they will be transferred literally into the exported > document. In particular, you can also embed beamer-specific > commands. > > 1.9 Example > > Here is a (still very incomplete) example Org document that is > intended for beamer export. > > #+LaTeX_CLASS: beamer > #+TITLE: Example Presentation > #+AUTHOR: Carsten Dominik > > * This is the first structural section > ** Frame 1 \\ with a subtitle > *** columns will be used > 0.3 > * Thanks :B_block:
