1
% $Header: /cvsroot/latex-beamer/latex-beamer/doc/beamerug-emulation.tex,v 1.7 2004/10/13 10:52:08 tantau Exp $
3
% Copyright 2003, 2004 by Till Tantau <tantau@users.sourceforge.net>.
5
% This program can be redistributed and/or modified under the terms
6
% of the GNU Public License, version 2.
10
\section[How To Import Presentations Based on Other Packages and Classes]
11
{How To Import Presentations Based on\\ Other Packages and Classes}
13
The \beamer\ class comes with a number of emulation layers for classes
14
or packages that do not support \beamer\ directly. For example, the
15
package |beamerseminar| maps some (not all) commands of the \seminar\
16
class to appropriate \beamer\ commands. This way, individual slides or
17
whole sets of slides that have been prepared for a presentation using
18
\seminar\ can be used inside \beamer, provided they are reasonably
21
None of the emulation layers is a perfect substitute for the original
22
(emulations seldom are) and it is not intended that they ever will
23
be. If you want/need/prefer the features of another class, use that
24
class for preparing your presentations. The intension of these layers
25
is just to help speed up creating \beamer\ presentations that use
26
parts of old presentations. You can simply copy these parts in
27
verbatim, without having to worry about the subtle differences in
30
A useful effect of using an emulation layer is that you get access to
31
all the features of \beamer\ while using the syntax of another
32
class. For example, you can use the |article| mode to create a
33
nice article version of a \prosper\ talk.
37
\subsection{Prosper and HA-Prosper}
38
\label{section-prosper}
40
The package |beamerprosper| maps the commands of the \prosper\
41
package, developed by Fr\'ed\'eric Goualard, to \beamer\
42
commands. Also, some commands of the \textsc{ha}-\prosper\ package,
43
developed by Hendri Adriaens, are mapped to \beamer\ commands.
44
\emph{These mappings cannot perfectly emulate all of Prosper!} Rather,
45
these mappings are intended as an aid when porting parts of
46
presentations created using \prosper\ to \beamer. \emph{No styles are
47
implemented that mimick Prosper styles.} Rather, the normal \beamer\
48
themes must be used (although, one could implement \beamer\ themes
49
that mimicks existing \prosper\ styles; I have not done that and do
52
The workflow for creating a \beamer\ presentation that uses \prosper\
53
code is the following:
56
Use the document class |beamer|, not |prosper|. Most options
57
passed to |prosper| do not apply to |beamer| and should be omitted.
59
Add a |\usepackage{beamerprosper}| to start the emulation.
61
If you add slides relying on \textsc{ha}-\prosper, you may wish to
62
add the option |framesassubsections| to |beamerprosper|, though I do
63
not recommend it (use the normal |\subsection| command instead; it
64
gives you more fine-grained control).
66
If you also copy the title commands, it may be necessary to adjust
67
the content of commands like |\title|
68
or |\author|. Note that in \prosper\ the |\email| command is given
69
outside the |\author| command, whereas in \beamer\ and also in
70
\textsc{ha}-\prosper\ it is given inside.
72
When copying slides containing the command |\includegraphics|, you
73
will almost surely have to adjust its usage. If you use pdf\LaTeX\
74
to typeset the presentation, than you cannot include PostScript
75
file. You should convert them to |.pdf| or to |.png| and adjust any
76
usage of |\includegraphics| accordingly.
78
When starting to change things, you can use all of \beamer's
79
commands and even mix them with \prosper\ commands.
82
An example can be found in the file |beamerexample-prosper.tex|.
84
There are, unfortunately, quite a few places where you may run into
88
In \beamer, the command |\PDForPS| will do exactly what the name
89
suggests: insert the first argument when run by |pdflatex|, insert
90
the second argument when run by |latex|. However, in \prosper, the
91
code inserted for the \pdf\ case is actually PostScript code, which
92
is only later converted to \pdf\ by some external program. You will
93
need to adjust this PostScript code such that it works with
94
|pdflatex| (which is not always possible).
96
If you used fine-grained spacing commands, like adding a little
97
horizontal skip here and a big negative vertical skip there, the
98
typesetting of the text may be poor. It may be a good idea to just
99
remove these spacing commands.
101
If you use |pstricks| commands, you will either have to stick to
102
using |latex| and |dvips| or will have to work around them using,
103
for example, |pgf|. Porting lot's of |pstricks| code is bound to be
104
difficult, if you wish to switch over to |pdflatex|, so be warned.
106
If the file cannot be compiled because some \prosper\ command is not
107
implemented, you will have to delete this command and try to mimick
108
its behaviour using some \beamer\ command.
112
\begin{package}{{beamerprosper}}
113
Include this package in a |beamer| presentation to get access to
114
\prosper\ commands. Use |beamer| as the document class, not
115
|prosper|. Most of the options passed to the class |prosper| make no
116
sense in |beamer|, so just delete them.
118
This package takes the following options:
121
\declare{|framesassubsections|} causes each frame to create its
122
own subsection with the frame title as subsection name. This
123
behaviour mimicks \textsc{ha}-\textsc{prosper}'s behaviour. In a
124
long talk this will create way too many subsections.
128
The |framesassubsections| option has no effect in |article| mode.
132
\documentclass[notes]{beamer}
134
\usepackage[framesassubsections]{beamerprosper}
136
\title{A Beamer Presentation Using (HA-)Prosper Commands}
137
\subtitle{Subtitles Are Also Supported}
139
\institution{The Institution is Mapped To Institute}
145
\tsectionandpart{Introduction}
148
\begin{slide}{About this file}
151
This is a beamer presentation.
153
You can use the prosper and the HA-prosper syntax.
155
This is done by mapping prosper and HA-prosper commands to beamer
158
The emulation is by no means perfect.
163
\section{Second Section}
164
\subsection{A subsection}
166
\frametitle{A frame created using the \texttt{frame} environment.}
168
\begin{itemize}[<+->]
169
\item You can still use the original beamer syntax.
170
\item The emulation is intended only to make recycling slides
171
easier, not to install a whole new syntax for beamer.
175
\begin{notes}{Notes for these slides}
176
My notes for these slides.
181
You can run, for example, pdf\LaTeX\ on the file to get a \beamer\
182
presentation with overlays. Adding the |notes| option will also show
183
the note. Certain commands, like |\LeftFoot|, are ignored. You can
184
change the theme using the usual commands. You can also use all
185
normal \beamer\ commands and concepts, like overlay-specifications,
186
in the file. You can also create an |article| version by using the
187
class |article| and including the package |beamerarticle|.
190
In the following, the effect of \prosper\ commands in \beamer\ are
193
\begin{command}{\email\marg{text}}
194
Simply typesets its argument in typewriter text. Should hence be
195
given \emph{inside} the |\author| command.
198
\begin{command}{\institution\marg{text}}
199
This command is mapped to \beamer's |\institute|
200
command if given \emph{outside} the |\author| command, otherwise it
201
typesets its argument in a smaller font.
204
\begin{command}{\Logo\opt{|(|\meta{x}|,|\meta{y}|)|}\marg{logo text}}
205
This is mapped to |\logo{|\meta{logo text}|}|. The coordinates are ignored.
208
\begin{environment}{{slides}\oarg{options}\marg{frame title}}
209
Inserts a frame with the |fragile=singleslide| option set. The
210
\meta{frame title} will be enclosed in a |\frametitle| command.
212
The following \meta{options} may be given:
215
\declare{|trans=|\meta{prosper transition}} installs the specified
216
\meta{prosper transition} as the transition effect when showing
219
\declare{\meta{prosper transition}} has the same effect as
220
|trans=|\meta{prosper transition}.
222
\declare{|toc=|\meta{entry}} overrides the subsection table of
223
contents entry created by this slide by \meta{entry}. Note that a
224
subsection entry is created for a slide only if the
225
|framesassubsections| options is specified.
227
\declare{|template|=\meta{text}} is ignored.
230
\example The following two texts have the same effect:
233
\begin{slide}[trans=Glitter,toc=short]{A Title}
241
\subsection{short} % omitted, if framesassubsections is not specified
242
\begin{frame}[fragile=singleslide]
251
\begin{command}{\overlays\marg{number}\marg{slide environment}}
252
This will put the \meta{slide environment} into a frame that does
253
not have the |fragile| option and which can hence contain
254
overlayed text. The \meta{number} is ignored since the number of
255
necessary overlays is computed automatically by \beamer.
257
\example The following code fragments have the same effect:
261
\begin{slide}{A Title}
272
\subsection{A Title} % omitted, if framesassubsections is not specified
284
\begin{command}{\fromSlide\marg{slide number}\marg{text}}
285
This is mapped to |\uncover<|\meta{slide number}|->{|\meta{text}|}|.
288
\begin{command}{\fromSlide|*|\marg{slide number}\marg{text}}
289
This is mapped to |\only<|\meta{slide number}|->{|\meta{text}|}|.
292
\begin{command}{\onlySlide\marg{slide number}\marg{text}}
293
This is mapped to |\uncover<|\meta{slide number}|>{|\meta{text}|}|.
296
\begin{command}{\onlySlide|*|\marg{slide number}\marg{text}}
297
This is mapped to |\only<|\meta{slide number}|>{|\meta{text}|}|.
300
\begin{command}{\untilSlide\marg{slide number}\marg{text}}
301
This is mapped to |\uncover<-|\meta{slide number}|>{|\meta{text}|}|.
304
\begin{command}{\untilsSlide|*|\marg{slide number}\marg{text}}
305
This is mapped to |\only<-|\meta{slide number}|>{|\meta{text}|}|.
308
\begin{command}{\FromSlide\marg{slide number}}
309
This is mapped to |\onslide<|\meta{slide number}|->|.
312
\begin{command}{\OnlySlide\marg{slide number}}
313
This is mapped to |\onslide<|\meta{slide number}|>|.
316
\begin{command}{\UntilSlide\marg{slide number}}
317
This is mapped to |\onslide<-|\meta{slide number}|>|.
320
\begin{command}{\slideCaption\marg{text}}
321
This is mapped to |\date{|\meta{text}|}|.
324
\begin{command}{\fontTitle\marg{text}}
325
Simply inserts \meta{text}.
328
\begin{command}{\fontText\marg{text}}
329
Simply inserts \meta{text}.
332
\begin{command}{\PDFtransition\marg{prosper transition}}
333
Maps the \meta{prosper transition} to an appropriate |\transxxxx|
337
\begin{environment}{{Itemize}}
338
This is mapped to |itemize|.
341
\begin{environment}{{itemstep}}
342
This is mapped to |itemize| with the option |[<+->]|.
345
\begin{environment}{{enumstep}}
346
This is mapped to |enumerate| with the option |[<+->]|.
349
\begin{command}{\hiddenitem}
350
This is mapped to |\addtocounter{beamerpauses}{1}|.
353
\begin{command}{\prosperpart\oarg{options}\marg{text}}
354
This command has the same effect as \prosper's |\part|
355
command. \beamer's normal |\part| command retains its normal
356
semantics. Thus, you might wish to replace all occurrences of |\part|
361
\begin{command}{\tsection\opt{|*|}\marg{section name}}
362
Creates a section named \meta{section name}. The star, if present,
366
\begin{command}{\tsectionandpart\opt{|*|}\marg{part text}}
367
Mapped to a |\section| command followed by a |\prosperpart|
371
In |article| mode, no part page is added.
374
\begin{command}{\dualslide\oarg{x}\oarg{y}\oarg{z}\marg{options}\marg{left
375
column}\marg{right column}}
376
This command is mapped to a |columns| environment. The \meta{left
377
column} text is shown in the left column, the \meta{right column}
378
text is shown in the right column. The options \meta{x}, \meta{y},
379
and \meta{z} are ignored. Also, all \emph{options} are ignored,
380
except for \declare{|lcolwidth=|} and \declare{|rcolwidth=|}. These
381
set the width of the left or right column, respectively.
384
\begin{command}{\PDForPS\marg{PostScript text}\marg{PDF text}}
385
Inserts either the \meta{PostScript text} or the \meta{PDF text},
386
depending on whether |latex| or |pdflatex| is used. When porting,
387
the \meta{PDF text} will most likely be \emph{incorrect}, since in
388
\prosper\ the \meta{PDF text} is actually PostScript text that is
389
later transformed to \pdf\ by some external program.
391
If the \meta{PDF text} contains an |\includegraphics| command (which
392
is its usual use), you should change the name of the graphic file
393
that is included to a name ending |.pdf|, |.png|, or
394
|.jpg|. Typically, you will have to convert your graphic to this
398
\begin{command}{\onlyInPDF\meta{PDF text}}
399
The \meta{PDF text} is only included if |pdflatex| is used. The same
400
as for the command |\PDForPS| applies here.
403
\begin{command}{\onlyInPS\meta{PS text}}
404
The \meta{PS text} is only included if |latex| is used.
407
\begin{environment}{{notes}\marg{title}}
408
Mapped to |\note{\textbf{|\meta{title}|}|\meta{environment contents}|}|
412
The following commands are parsed by \beamer, but have no effect:
413
\begin{itemize}\itemsep=0pt\parskip=0pt
418
\item |\DefaultTransition|,
419
\item |\NoFrenchBabelItemize|,
420
\item |\TitleSlideNav|,
421
\item |\NormalSlideNav|,
423
\item |\LeftFoot|, and
431
\label{section-seminar}
433
The package |beamerseminar| maps a subset of the commands of the \seminar\
434
package to \beamer. As for \prosper, the emulation cannot be
435
perfect. For example, no portrait slides are supported, no
436
automatic page breaking, the framing of slides is not
437
emulated. Unfortunately, for all frames (|slide| environments) that
438
contain overlays, you have to put the environment into a |frame|
439
environment ``by hand'' and must remove all occurrences of |\newslide|
440
inside the environment by closing the slide and opening a new one (and
441
then putting these into |frame| environments).
443
The workflow for the migration is the following:
446
Use the document class |beamer|, not |seminar|. Most options
447
passed to |seminar| do not apply to |beamer| and should be
450
If you copy parts of a presentation that is mixed with normal text,
451
add the |ignorenonframetext| option and place \emph{every} |slide|
452
environment inside a |frame| since \beamer\ will not recognize the
453
|\begin{slide}| as the beginning of a frame.
455
Add a |\usepackage{beamerseminar}| to start the emulation. Add the
456
option |accumulate| if you wish to create a presentation to be held
457
with a video projector.
459
Possibly add commands to install themes and templates.
461
The should be not commands in the preamble having to do with
462
page and slide styles. They do not apply to |beamer|.
464
If a |\newslide| command is used in a |slide| (or similarly
465
|slide*|) environment that contains an overlay, you must replace it
466
by a closing |\end{slide}| and an opening |\begin{slide}|.
468
Next, for each |slide| or |slide*| environment that contains an
469
overlay, you must place a |frame| environment around it. You can
470
remove the |slide| environment (and hence effectively replace it by
471
|frame|), unless you use the |accumulate| option.
473
If you use |\section| or |\subsection| commands inside slides, you
474
will have to move them \emph{outside} the frames. It may then be
475
necessary to add a |\frametitle| command to the slide.
477
If you use pdf\LaTeX\ to typeset the presentation, you cannot
478
include PostScript files. You should convert them to |.pdf| or to
479
|.png| and adjust any usage of |\includegraphics| accordingly.
481
When starting to change things, you can use all of \beamer's
482
commands and even mix them with \seminar\ commands.
485
An example can be found in the file |beamerexample-seminar.tex|.
487
There are, unfortunately, numerous places where you may run into
491
The whole |note| management of |seminar| is so different from
492
|beamer|'s, that you will have to edit notes ``by hand.'' In
493
particular, commands like |\ifslidesonly| and |\ifslide| may not do
494
exactly what you expect.
496
If you use |pstricks| commands, you will either have to stick to
497
using |latex| and |dvips| or will have to work around them using,
498
for example, |pgf|. Porting lot's of |pstricks| code is bound to be
499
difficult, if you wish to switch over to |pdflatex|, so be warned.
501
If the file cannot be compiled because some \seminar\ command is not
502
implemented, you will have to delete this command and try to mimick
503
its behaviour using some \beamer\ command.
506
\begin{package}{{beamerseminar}}
507
Include this package in a |beamer| presentation to get access to
508
\seminar\ commands. Use |beamer| as the document class, not
509
|seminar|. Most of the options passed to the class |seminar| make no
510
sense in |beamer|, so just delete them.
512
This package takes the following options:
515
\declare{|accumulate|} causes overlays to be accumulated. The
516
original behaviour of the \seminar\ package is that in each
517
overlay only the really ``new'' part of the overlay is shown. This
518
makes sense, if you really print out the overlays on
519
transparencies and then really stack overlays on top of each
520
other. For a presentation with a video projector, you rather
521
want to present an ``accumulated'' version of the overlays. This
522
is what this option does: When the new material of the $i$th
523
overlay is shown, the material of all previous overlays is also
528
The following example is an extract of |beamerexample-seminar.tex|:
530
\documentclass[ignorenonframetext]{beamer}
531
\usepackage[accumulated]{beamerseminar}
532
\usepackage{beamerthemeclassic}
534
\title{A beamer presentation using seminar commands}
537
\let\heading=\frametitle
545
This is some text outside any frame. It will only be shown in the
550
\heading{This is a frame title.}
554
\item Overlays are a little tricky in seminar.
556
\item But it is possible to use them in beamer.
565
You can use all normal \beamer\ commands and concepts, like
566
overlay-specifications, in the file. You can also create an
567
|article| version by using the class |article| and
568
including the package |beamerarticle|.
571
In the following, the effect of \seminar\ commands in \beamer\ are
574
\begin{command}{\overlay\marg{number}}
575
Shows the material till the end of the current \TeX\ group only on
576
overlay numbered $\hbox{\meta{number}}+1$ or, if the |accumulate|
577
option is given, from that overlay on. Usages of this command may be
578
nested (as in \seminar). If an |\overlay| command is given inside
579
another, it temporarily ``overrules'' the outer one as demonstrated
580
in the following example, where it is assumed that the |accumulate|
587
This is shown from the first slide on.
589
This is shown from the third slide on.
591
This is shown from the second slide on.
593
This is shown once more from the third slide on.
601
\begin{environment}{{slide}\opt{|*|}}
602
Mainly installs an |\overlay{0}| around the \meta{environment
603
contents}. If the |accumulate| option is given, this has no
604
effect, but otherwise it will cause the main text of the slide to be
605
shown \emph{only} on the first slide. This is useful if you really
606
wish to physically place slides on top of each other.
608
The starred version does the same as the nonstarred one.
610
If this command is not issued inside a |\frame|, it sets up a frame
611
with the |fragile=singleframe| option set. Thus, this frame will
612
contain only a single slide.
622
Some text. And an {\overlay{1} overlay}.
628
\begin{command}{\red}
629
Mapped to |\color{red}|.
632
\begin{command}{\blue}
633
Mapped to |\color{blue}|.
636
\begin{command}{\green}
637
Mapped to |\color{green}|.
640
\begin{command}{\ifslide}
641
True in the |presentation| modes, false in the |article| mode.
644
\begin{command}{\ifslidesonly}
648
\begin{command}{\ifarticle}
649
False in the |presentation| modes, true in the |article| mode.
652
\begin{command}{\ifportrait}
656
The following commands are parsed by \beamer, but have no effect:
657
\begin{itemize}\itemsep=0pt\parskip=0pt
663
\subsection{Foil\TeX}
664
\label{section-foiltex}
666
The package |beamerfoils| maps a subset of the commands of the \foils\
667
package to \beamer. Since this package defines only few non-standard
668
\TeX\ commands and since \beamer\ implements all the standard
669
commands, the emulation layer is pretty simple.
671
A copyright notice: The Foil\TeX\ package has a restricted
672
license. For this reason, no example from the \foils\ package is
673
included in the \beamer\ class. The emulation itself does not use the
674
code of the \foils\ package (rather, it just maps \foils\ commands to
675
\beamer\ commands). For this reason, my understanding is that the
676
\emph{emulation} offered by the \beamer\ class is ``free'' and legally
677
so. IBM has a copyright on the \foils\ class, not on the effect the
678
commands of this class have. (At least, that's my understanding of
681
The workflow for the migration is the following:
684
Use the document class |beamer|, not |foils|.
686
Add a |\usepackage{beamerfoils}| to start the emulation.
688
Possibly add commands to install themes and templates.
690
If the command |\foilhead| is used inside a |\frame| command or
691
|frame| environment, it behaves like |\frametitle|. If it used
692
outside a frame, it will start a new frame (with the
693
|allowframebreaks| option, thus no overlays are allowed). This frame
694
will persist till the next occurrence of |\foilhead| or of the new
695
command |\endfoil|. Note that a |\frame| command will \emph{not} end
696
a frame started using |\foilhead|.
698
If you rely on automatic frame creation based on |\foilhead|, you
699
will need to insert an |\endfoil| before the end of the document to
702
If you use pdf\LaTeX\ to typeset the presentation, than you cannot
703
include PostScript files. You should convert them to |.pdf| or to
704
|.png| and adjust any usage of |\includegraphics| accordingly.
706
Sizes of objects are different in \beamer, since the scaling is done
707
by the viewer, not by the class. Thus a framebox of size 6 inches
708
will be way too big in a \beamer\ presentation. You will have to
709
manually adjust explicit dimension occurring in a foil\TeX\ presentation.
712
\begin{package}{{beamerfoils}}
713
Include this package in a |beamer| presentation to get access to
714
\foils\ commands. Use |beamer| as the document class, not
717
\example In the following example, frames are automatically
718
created. The |\endfoil| at the end is needed to close the last
721
\documentclass{beamer}
722
\usepackage{beamerfoils}
728
\foilhead{First Frame}
730
This is on the first frame.
732
This is on the second frame, which is a continuation of the first.
734
\foilhead{Third Frame}
736
This is on the third frame.
742
\example In this example, frames are manually inserted. No
743
|\endfoil| is needed.
745
\documentclass{beamer}
746
\usepackage{beamerfoils}
753
\foilhead{First Frame}
754
This is on the first frame.
758
\foilhead{Second Frame}
759
This is on the second frame.
766
In the following, the effect of \foils\ commands in \beamer\ are
769
\begin{command}{\MyLogo\marg{logo text}}
770
This is mapped to |\logo|, though the logo is internally stored,
771
such that it can be switched on and off using |\LogoOn| and |\LogoOff|.
774
\begin{command}{\LogoOn}
775
Makes the logo visible.
778
\begin{command}{\LogoOff}
779
Makes the logo invisible.
782
\begin{command}{\foilhead\oarg{dimension}\marg{frame title}}
783
If used inside a |\frame| command or |frame| environment, this is
784
mapped to |\frametitle{|\meta{frame title}|}|. If used outside any
785
frames, a new frame is started with the option
786
|allowframebreaks|. If a frame was previously started using this
787
command, it will be closed before the next frame is started. The
788
\meta{dimension} is ignored.
791
\begin{command}{\rotatefoilhead\oarg{dimension}\marg{frame title}}
792
This command has exactly the same effect as |\foilhead|.
795
\begin{command}{\endfoil}
796
This is a command that is \emph{not} available in \foils. In
797
\beamer, it can be used to end a frame that has automatically been
798
opened using |\foildhead|. This command must be given before the end
799
of the document if the last frame was opened using |\foildhead|.
802
\begin{environment}{{boldequation}\opt{|*|}}
803
This is mapped to the |equation| or the |equation*| environment,
804
with |\boldmath| switched on.
807
\begin{command}{\FoilTeX}
808
Typesets the foil\TeX\ name as in the \foils\ package.
811
\begin{command}{\bm\marg{text}}
812
Implemented as in the \foils\ package.
815
\begin{command}{\bmstyle\marg{text}\marg{more text}}
816
Implemented as in the \foils\ package.
819
The following additional theorem-like environments are predefined:
824
\item |Proposition*|,
827
For example, the first is defined using |\newtheorem*{Theorem*}{Theorem}|.
829
The following commands are parsed by \beamer, but have not effect:
832
\item |\rightheader|,
834
\item |\rightfooter|,
835
\item |\Restriction|, and
841
\subsection{\TeX Power}
842
\label{section-texpower}
844
The package |beamertexpower| maps a subset of the commands of the
845
\texpower\ package, due to Stephan Lehmke, to \beamer. This subset is
846
currently rather small, so a lot of adaptions may be necessary. Note
847
that \texpower\ is not a full class by itself, but a package that
848
needs another class, like |seminar| or |prosper| to do the actually
849
typesetting. It may thus be necessary to additionally load an
850
emulation layer for these also. Indeed, it \emph{might} be possible to
851
directly use \texpower\ inside \beamer, but I have not tried
852
that. Perhaps this will be possible in the future.
854
Currently, the package |beamertexpower| mostly just maps the
855
|\stepwise| and related commands to appropriate \beamer\ commands. The
856
|\pause| command need not be mapped since it is directly implemented
859
The workflow for the migration is the following:
862
Replace the document class by |beamer|. If the document class is
863
|seminar| or |prosper|, you can use the above emulation layers, that
864
is, you can include the files |beamerseminar| or |beamerprosper| to
867
All notes on what to do for the emulation of \seminar\ or \prosper\
870
Additionally, add |\usepackage{beamertexpower}| to start the
875
\begin{package}{{beamertexpower}}
876
Include this package in a |beamer| presentation to get access to the
877
\texpower\ commands having to do with the |\stepwise| command.
880
A note on the |\pause| command: Both \beamer\ and \texpower\ implement
881
this command and they have the same semantics; so there is no need to
882
map this command to anything different in |beamertexpower|. However, a
883
difference is that |\pause| can be used almost anywhere in \beamer,
884
whereas is may only be used in non-nested situations in \texpower. Since
885
\beamer\ is only more flexible than \texpower\ here, this will not
886
cause problems when porting.
888
In the following, the effect of \texpower\ commands in \beamer\ are
891
\begin{command}{\stepwise\marg{text}}
892
As in \TeX Power, this initiates text in which commands like |\step|
893
or |\switch| may be given. Text contained in a |\step| command will
894
be enclosed in an |\only| command with the overlay specification
895
|<+(1)->|. This means that the text of the first |\step| is inserted
896
from the second slide onward, the text of the second |\step| is
897
inserted from the third slide onward, and so on.
900
\begin{command}{\parstepwise\marg{text}}
901
Same as |\stepwise|, only |\uncover| is used instead of |\only| when
902
mapping the |\step| command.
905
\begin{command}{\liststepwise\marg{text}}
906
Same as |\stepwise|, only an invisible horizontal line is inserted
907
before the \meta{text}. This is presumable useful for solving some
908
problems related to vertical spacing in \texpower.
911
\begin{command}{\step\marg{text}}
912
This is either mapped to |\only<+(1)->|\meta{text} or to
913
|\uncover<+(1)->|\meta{text}, depending on whether this command is
914
used inside a |\stepwise| environment or inside a |\parstepwise|
918
\begin{command}{\steponce\marg{text}}
919
This is either mapped to |\only<+(1)>|\meta{text} or to
920
|\uncover<+(1)>|\meta{text}, depending on whether this command is
921
used inside a |\stepwise| environment or inside a |\parstepwise|
925
\begin{command}{\switch\marg{alternate text}\marg{text}}
926
This is mapped to |\alt<+(1)->{|\meta{text}|}{|\meta{alternate
927
text}|}|. Note that the arguments are swapped.
930
\begin{command}{\bstep\marg{text}}
931
This is always mapped to |\uncover<+(1)->|\meta{text}.
934
\begin{command}{\dstep}
935
This just advances the counter |beamerpauses| by one. It has no
939
\begin{command}{\vstep}
943
\begin{command}{\restep\marg{text}}
944
Same as |\step|, but the \meta{text} is shown one the same slide as
945
the previous |\step| command. This is implemented by first
946
decreasing the countern |beamerpauses| by one before calling
950
\begin{command}{\reswitch\marg{alternate text}\meta{text}}
951
Like |\restep|, only for the |\switch| command.
954
\begin{command}{\rebstep\meta{text}}
955
Like |\restep|, only for the |\bstep| command.
958
\begin{command}{\redstep}
959
This command has no effect.
962
\begin{command}{\revstep}
963
This command has no effect.
966
\begin{command}{\boxedsteps}
967
Temporarily (for the current \TeX\ group) changes the effect of
968
|\step| to issue an |\uncover|, even if used inside a |\stepwise|
972
\begin{command}{\nonboxedsteps}
973
Temporarily (for the current \TeX\ group) changes the effect of
974
|\step| to issue an |\only|, even if used inside a |\parstepwise|
978
\begin{command}{\code\marg{text}}
979
Typesets the argument using a boldface typewriter font.
982
\begin{command}{\codeswitch}
983
Switches to a boldface typewriter font.
991
%%% TeX-master: "beameruserguide"
added
removed
doc/beamerug-emulation.tex
