Debian Codegraph @

texmf-dist/doc/latex/beamer/beamerug-emulation.tex

raw
1 % !TeX root = beameruserguide.tex
2 % Copyright 2003--2007 by Till Tantau
3 % Copyright 2010 by Vedran Mileti\'c
4 % Copyright 2015 by Vedran Mileti\'c, Joseph Wright
5 %
6 % This file may be distributed and/or modified
7 %
8 % 1. under the LaTeX Project Public License and/or
9 % 2. under the GNU Free Documentation License.
10 %
11 % See the file LICENSE.md for more details.
12
13 \section[How To Import Presentations Based on Other Packages and Classes]{How To Import Presentations Based on\\ Other Packages and Classes}
14
15 The \beamer\ class comes with a number of emulation layers for classes or packages that do not support \beamer\ directly. For example, the package |beamerseminar| maps some (not all) commands of the \seminar\ class to appropriate \beamer\ commands. This way, individual slides or whole sets of slides that have been prepared for a presentation using \seminar\ can be used inside \beamer, provided they are reasonably simple.
16
17 None of the emulation layers is a perfect substitute for the original (emulations seldom are) and it is not intended that they ever will be. If you want/need/prefer the features of another class, use that class for preparing your presentations. The intention of these layers is just to help speed up creating \beamer\ presentations that use parts of old presentations. You can simply copy these parts in verbatim, without having to worry about the subtle differences in syntax.
18
19 A useful effect of using an emulation layer is that you get access to all the features of \beamer\ while using the syntax of another class. For example, you can use the |article| mode to create a nice article version of a \prosper\ talk.
20
21
22 \subsection{Prosper, HA-Prosper and Powerdot}
23 \label{section-prosper}
24
25 The package |beamerprosper| maps the commands of the \prosper\ package, developed by Fr\'ed\'eric Goualard, to \beamer\ commands. Also, some commands of the \textsc{ha}-\prosper\ and \textsc{powerdot} packages, developed by Hendri Adriaens, are mapped to \beamer\ commands. \emph{These mappings cannot perfectly emulate all of Prosper!} Rather, these mappings are intended as an aid when porting parts of presentations created using \prosper\ to \beamer. \emph{No styles are implemented that mimic Prosper styles.} Rather, the normal \beamer\ themes must be used (although, one could implement \beamer\ themes that mimics existing \prosper\ styles; we have not done that and do not intend to).
26
27 The workflow for creating a \beamer\ presentation that uses \prosper\ code is the following:
28 \begin{enumerate}
29 \item
30 Use the document class |beamer|, not |prosper|. Most options passed to |prosper| do not apply to |beamer| and should be omitted.
31 \item
32 Add a |\usepackage{beamerprosper}| to start the emulation.
33 \item
34 If you add slides relying on \textsc{ha}-\prosper, you may wish to add the option |framesassubsections| to |beamerprosper|, though we do not recommend it (use the normal |\subsection| command instead; it gives you more fine-grained control).
35 \item
36 If you also copy the title commands, it may be necessary to adjust the content of commands like |\title| or |\author|. Note that in \prosper\ the |\email| command is given outside the |\author| command, whereas in \beamer\ and also in \textsc{ha}-\prosper\ it is given inside.
37 \item
38 When copying slides containing the command |\includegraphics|, you will almost surely have to adjust its usage. If you use pdf\LaTeX\ to typeset the presentation, than you cannot include PostScript files. You should convert them to |.pdf| or to |.png| and adjust any usage of |\includegraphics| accordingly.
39 \item
40 When starting to change things, you can use all of \beamer's commands and even mix them with \prosper\ commands.
41 \end{enumerate}
42
43 An example can be found in the file |beamerexample-prosper.tex|.
44
45 There are, unfortunately, quite a few places where you may run into problems:
46 \begin{itemize}
47 \item
48 In \beamer, the command |\PDForPS| will do exactly what the name suggests: insert the first argument when run by |pdflatex|, insert the second argument when run by |latex|. However, in \prosper, the code inserted for the \pdf\ case is actually PostScript code, which is only later converted to \pdf\ by some external program. You will need to adjust this PostScript code such that it works with |pdflatex| (which is not always possible).
49 \item
50 If you used fine-grained spacing commands, like adding a little horizontal skip here and a big negative vertical skip there, the typesetting of the text may be poor. It may be a good idea to just remove these spacing commands.
51 \item
52 If you use |pstricks| commands, you will either have to stick to using |latex| and |dvips| or will have to work around them using, for example, |pgf|. Porting lots of |pstricks| code is bound to be difficult, if you wish to switch over to |pdflatex|, so be warned. You can read more about that in Section~\ref{section-graphics} that talks about graphics.
53 \item
54 If the file cannot be compiled because some \prosper\ command is not implemented, you will have to delete this command and try to mimic its behavior using some \beamer\ command.
55 \end{itemize}
56
57 \begin{package}{{beamerprosper}}
58 Include this package in a |beamer| presentation to get access to \prosper\ commands. Use |beamer| as the document class, not |prosper|. Most of the options passed to the class |prosper| make no sense in |beamer|, so just delete them.
59
60 This package takes the following options:
61 \begin{itemize}
62 \item
63 \declare{|framesassubsections|} causes each frame to create its own subsection with the frame title as subsection name. This behavior mimics \textsc{ha}-\textsc{prosper}'s behavior. In a long talk this will create way too many subsections.
64 \end{itemize}
65
66 \articlenote
67 The |framesassubsections| option has no effect in |article| mode.
68
69 \example
70 \begin{verbatim}
71 \documentclass[notes]{beamer}
72
73 \usepackage[framesassubsections]{beamerprosper}
74
75 \title{A Beamer Presentation Using (HA-)Prosper Commands}
76 \subtitle{Subtitles Are Also Supported}
77 \author{Till Tantau}
78 \institution{The Institution is Mapped To Institute}
79
80 \begin{document}
81
82 \maketitle
83
84 \tsectionandpart{Introduction}
85
86 \overlays{2}{
87 \begin{slide}{About this file}
88 \begin{itemstep}
89 \item
90 This is a beamer presentation.
91 \item
92 You can use the prosper and the HA-prosper syntax.
93 \item
94 This is done by mapping prosper and HA-prosper commands to beamer
95 commands.
96 \item
97 The emulation is by no means perfect.
98 \end{itemstep}
99 \end{slide}
100 }
101
102 \section{Second Section}
103 \subsection{A subsection}
104 \begin{frame}
105 \frametitle{A frame created using the \texttt{frame} environment.}
106
107 \begin{itemize}[<+->]
108 \item You can still use the original beamer syntax.
109 \item The emulation is intended only to make recycling slides
110 easier, not to install a whole new syntax for beamer.
111 \end{itemize}
112 \end{frame}
113
114 \begin{notes}{Notes for these slides}
115 My notes for these slides.
116 \end{notes}
117 \end{document}
118 \end{verbatim}
119 You can run, for example, pdf\LaTeX\ on the file to get a \beamer\ presentation with overlays. Adding the |notes| option will also show the notes. Certain commands, like |\LeftFoot|, are ignored. You can change the theme using the usual commands. You can also use all normal \beamer\ commands and concepts, like overlay-specifications, in the file. You can also create an |article| version by using the class |article| and including the package |beamerarticle|.
120 \end{package}
121
122 In the following, the effects of \prosper\ commands in \beamer\ are listed.
123
124 \begin{command}{\email\marg{text}}
125 Simply typesets its argument in typewriter text. Should hence be given \emph{inside} the |\author| command.
126 \end{command}
127
128 \begin{command}{\institution\marg{text}}
129 This command is mapped to \beamer's |\institute| command if given \emph{outside} the |\author| command, otherwise it typesets its argument in a smaller font.
130 \end{command}
131
132 \begin{command}{\Logo\opt{|(|\meta{x}|,|\meta{y}|)|}\marg{logo text}}
133 This is mapped to |\logo{|\meta{logo text}|}|. The coordinates are ignored.
134 \end{command}
135
136 \begin{environment}{{slide}\oarg{options}\marg{frame title}}
137 Inserts a frame with the |fragile=singleslide| option set. The \meta{frame title} will be enclosed in a |\frametitle| command.
138
139 The following \meta{options} may be given:
140 \begin{itemize}
141 \item
142 \declare{|trans=|\meta{prosper transition}} installs the specified \meta{prosper transition} as the transition effect when showing the slide.
143 \item
144 \declare{\meta{prosper transition}} has the same effect as |trans=|\meta{prosper transition}.
145 \item
146 \declare{|toc=|\meta{entry}} overrides the subsection table of contents entry created by this slide by \meta{entry}. Note that a subsection entry is created for a slide only if the |framesassubsections| options is specified.
147 \item
148 \declare{|template|=\meta{text}} is ignored.
149 \end{itemize}
150
151 \example
152 The following two texts have the same effect:
153
154 \begin{verbatim}
155 \begin{slide}[trans=Glitter,toc=short]{A Title}
156 Hi!
157 \end{slide}
158 \end{verbatim}
159 and
160 \begin{verbatim}
161 \subsection{short} % omitted, if framesassubsections is not specified
162 \begin{frame}[fragile=singleslide]
163 \transglitter
164 \frametitle{A Title}
165 Hi!
166 \end{frame}
167 \end{verbatim}
168 \end{environment}
169
170 \begin{command}{\overlays\marg{number}\marg{slide environment}}
171 This will put the \meta{slide environment} into a frame that does not have the |fragile| option and which can hence contain overlaid text. The \meta{number} is ignored since the number of necessary overlays is computed automatically by \beamer.
172
173 \example
174 The following code fragments have the same effect:
175
176 \begin{verbatim}
177 \overlays{2}{
178 \begin{slide}{A Title}
179 \begin{itemstep}
180 \item Hi!
181 \item Ho!
182 \end{itemstep}
183 \end{slide}}
184 \end{verbatim}
185 and
186 \begin{verbatim}
187 \subsection{A Title} % omitted, if framesassubsections is not specified
188 \begin{frame}
189 \frametitle{A Title}
190 \begin{itemstep}
191 \item Hi!
192 \item Ho!
193 \end{itemstep}
194 \end{frame}
195 \end{verbatim}
196 \end{command}
197
198 \begin{command}{\fromSlide\marg{slide number}\marg{text}}
199 This is mapped to |\uncover<|\meta{slide number}|->{|\meta{text}|}|.
200 \end{command}
201
202 \begin{command}{\fromSlide|*|\marg{slide number}\marg{text}}
203 This is mapped to |\only<|\meta{slide number}|->{|\meta{text}|}|.
204 \end{command}
205
206 \begin{command}{\onlySlide\marg{slide number}\marg{text}}
207 This is mapped to |\uncover<|\meta{slide number}|>{|\meta{text}|}|.
208 \end{command}
209
210 \begin{command}{\onlySlide|*|\marg{slide number}\marg{text}}
211 This is mapped to |\only<|\meta{slide number}|>{|\meta{text}|}|.
212 \end{command}
213
214 \begin{command}{\untilSlide\marg{slide number}\marg{text}}
215 This is mapped to |\uncover<-|\meta{slide number}|>{|\meta{text}|}|.
216 \end{command}
217
218 \begin{command}{\untilSlide|*|\marg{slide number}\marg{text}}
219 This is mapped to |\only<-|\meta{slide number}|>{|\meta{text}|}|.
220 \end{command}
221
222 \begin{command}{\FromSlide\marg{slide number}}
223 This is mapped to |\onslide<|\meta{slide number}|->|.
224 \end{command}
225
226 \begin{command}{\OnlySlide\marg{slide number}}
227 This is mapped to |\onslide<|\meta{slide number}|>|.
228 \end{command}
229
230 \begin{command}{\UntilSlide\marg{slide number}}
231 This is mapped to |\onslide<-|\meta{slide number}|>|.
232 \end{command}
233
234 \begin{command}{\slideCaption\marg{text}}
235 This is mapped to |\date{|\meta{text}|}|.
236 \end{command}
237
238 \begin{command}{\fontTitle\marg{text}}
239 Simply inserts \meta{text}.
240 \end{command}
241
242 \begin{command}{\fontText\marg{text}}
243 Simply inserts \meta{text}.
244 \end{command}
245
246 \begin{command}{\PDFtransition\marg{prosper transition}}
247 Maps the \meta{prosper transition} to an appropriate |\transxxxx| command.
248 \end{command}
249
250 \begin{environment}{{Itemize}}
251 This is mapped to |itemize|.
252 \end{environment}
253
254 \begin{environment}{{itemstep}}
255 This is mapped to |itemize| with the option |[<+->]|.
256 \end{environment}
257
258 \begin{environment}{{enumstep}}
259 This is mapped to |enumerate| with the option |[<+->]|.
260 \end{environment}
261
262 \begin{command}{\hiddenitem}
263 This is mapped to |\addtocounter{beamerpauses}{1}|.
264 \end{command}
265
266 \begin{command}{\prosperpart\oarg{options}\marg{text}}
267 This command has the same effect as \prosper's |\part| command. \beamer's normal |\part| command retains its normal semantics. Thus, you might wish to replace all occurrences of |\part| by |\prosperpart|.
268 \end{command}
269
270 \begin{command}{\tsection\opt{|*|}\marg{section name}}
271 Creates a section named \meta{section name}. The star, if present, is ignored.
272 \end{command}
273
274 \begin{command}{\tsectionandpart\opt{|*|}\marg{part text}}
275 Mapped to a |\section| command followed by a |\prosperpart| command.
276
277 \articlenote
278 In |article| mode, no part page is added.
279 \end{command}
280
281 \begin{command}{\dualslide\oarg{x}\oarg{y}\oarg{z}\marg{options}\marg{left column}\marg{right column}}
282 This command is mapped to a |columns| environment. The \meta{left column} text is shown in the left column, the \meta{right column} text is shown in the right column. The options \meta{x}, \meta{y}, and \meta{z} are ignored. Also, all \meta{options} are ignored, except for \declare{|lcolwidth=|} and \declare{|rcolwidth=|}. These set the width of the left or right column, respectively.
283 \end{command}
284
285 \begin{command}{\PDForPS\marg{PostScript text}\marg{PDF text}}
286 Inserts either the \meta{PostScript text} or the \meta{PDF text}, depending on whether |latex| or |pdflatex| is used. When porting, the \meta{PDF text} will most likely be \emph{incorrect}, since in \prosper\ the \meta{PDF text} is actually PostScript text that is later transformed to \pdf\ by some external program.
287
288 If the \meta{PDF text} contains an |\includegraphics| command (which is its usual use), you should change the name of the graphic file that is included to a name ending |.pdf|, |.png|, or |.jpg|. Typically, you will have to convert your graphic to this format.
289 \end{command}
290
291 \begin{command}{\onlyInPDF\meta{PDF text}}
292 The \meta{PDF text} is only included if |pdflatex| is used. The same as for the command |\PDForPS| applies here.
293 \end{command}
294
295 \begin{command}{\onlyInPS\meta{PS text}}
296 The \meta{PS text} is only included if |latex| is used.
297 \end{command}
298
299 \begin{environment}{{notes}\marg{title}}
300 Mapped to |\note{\textbf{|\meta{title}|}|\meta{environment contents}|}| (more or less).
301 \end{environment}
302
303 The following commands are parsed by \beamer, but have no effect:
304 \begin{itemize}\itemsep=0pt\parskip=0pt
305 \item |\myitem|,
306 \item |\FontTitle|,
307 \item |\FontText|,
308 \item |\ColorFoot|,
309 \item |\DefaultTransition|,
310 \item |\NoFrenchBabelItemize|,
311 \item |\TitleSlideNav|,
312 \item |\NormalSlideNav|,
313 \item |\HAPsetup|,
314 \item |\LeftFoot|, and
315 \item |\RightFoot|.
316 \end{itemize}
317
318
319 \subsection{Seminar}
320 \label{section-seminar}
321
322 The package |beamerseminar| maps a subset of the commands of the \seminar\ package to \beamer. As for \prosper, the emulation cannot be perfect. For example, no portrait slides are supported, no automatic page breaking, the framing of slides is not emulated. Unfortunately, for all frames (|slide| environments) that contain overlays, you have to put the environment into a |frame| environment ``by hand'' and must remove all occurrences of |\newslide| inside the environment by closing the slide and opening a new one (and then putting these into |frame| environments).
323
324 The workflow for the migration is the following:
325 \begin{enumerate}
326 \item
327 Use the document class |beamer|, not |seminar|. Most options passed to |seminar| do not apply to |beamer| and should be omitted.
328 \item
329 If you copy parts of a presentation that is mixed with normal text, add the |ignorenonframetext| option and place \emph{every} |slide| environment inside a |frame| since \beamer\ will not recognize the |\begin{slide}| as the beginning of a frame.
330 \item
331 Add a |\usepackage{beamerseminar}| to start the emulation. Add the option |accumulated| if you wish to create a presentation to be held with a video projector.
332 \item
333 Possibly add commands to install themes and templates.
334 \item
335 There should not be commands in the preamble having to do with page and slide styles. They do not apply to |beamer|.
336 \item
337 If a |\newslide| command is used in a |slide| (or similarly |slide*|) environment that contains an overlay, you must replace it by a closing |\end{slide}| and an opening |\begin{slide}|.
338 \item
339 Next, for each |slide| or |slide*| environment that contains an overlay, you must place a |frame| environment around it. You can remove the |slide| environment (and hence effectively replace it by |frame|), unless you use the |accumulated| option.
340 \item
341 If you use |\section| or |\subsection| commands inside slides, you will have to move them \emph{outside} the frames. It may then be necessary to add a |\frametitle| command to the slide.
342 \item
343 If you use pdf\LaTeX\ to typeset the presentation, you cannot include PostScript files. You should convert them to |.pdf| or to |.png| and adjust any usage of |\includegraphics| accordingly.
344 \item
345 When starting to change things, you can use all of \beamer's commands and even mix them with \seminar\ commands.
346 \end{enumerate}
347
348 An example can be found in the file |beamerexample-seminar.tex|.
349
350 There are, unfortunately, numerous places where you may run into problems:
351 \begin{itemize}
352 \item
353 The whole |note| management of |seminar| is so different from |beamer|'s, that you will have to edit notes ``by hand.'' In particular, commands like |\ifslidesonly| and |\ifslide| may not do exactly what you expect.
354 \item
355 If you use |pstricks| commands, you will either have to stick to using |latex| and |dvips| or will have to work around them using, for example, |pgf|. Porting lots of |pstricks| code is bound to be difficult, if you wish to switch over to |pdflatex|, so be warned.
356 \item
357 If the file cannot be compiled because some \seminar\ command is not implemented, you will have to delete this command and try to mimic its behavior using some \beamer\ command.
358 \end{itemize}
359
360 \begin{package}{{beamerseminar}}
361 Include this package in a |beamer| presentation to get access to \seminar\ commands. Use |beamer| as the document class, not |seminar|. Most of the options passed to the class |seminar| make no sense in |beamer|, so just delete them.
362
363 This package takes the following options:
364 \begin{itemize}
365 \item
366 \declare{|accumulated|} causes overlays to be accumulated. The original behavior of the \seminar\ package is that in each overlay only the really ``new'' part of the overlay is shown. This makes sense, if you really print out the overlays on transparencies and then really stack overlays on top of each other. For a presentation with a video projector, you rather want to present an ``accumulated'' version of the overlays. This is what this option does: When the new material of the $i$-th overlay is shown, the material of all previous overlays is also shown.
367 \end{itemize}
368
369 \example
370 The following example is an extract of |beamerexample-seminar.tex|:
371
372 \begin{verbatim}
373 \documentclass[ignorenonframetext]{beamer}
374 \usepackage[accumulated]{beamerseminar}
375 \usepackage{beamerthemeclassic}
376
377 \title{A beamer presentation using seminar commands}
378 \author{Till Tantau}
379
380 \let\heading=\frametitle
381
382 \begin{document}
383
384 \begin{frame}
385 \maketitle
386 \end{frame}
387
388 This is some text outside any frame. It will only be shown in the
389 article version.
390
391 \begin{frame}
392 \begin{slide}
393 \heading{This is a frame title.}
394
395 \begin{enumerate}
396 {\overlay1
397 \item Overlays are a little tricky in seminar.
398 {\overlay2
399 \item But it is possible to use them in beamer.
400 }
401 }
402 \end{enumerate}
403 \end{slide}
404 \end{frame}
405 \end{document}
406 \end{verbatim}
407 You can use all normal \beamer\ commands and concepts, like overlay-specifications, in the file. You can also create an |article| version by using the class |article| and including the package |beamerarticle|.
408 \end{package}
409
410 In the following, the effects of \seminar\ commands in \beamer\ are listed.
411
412 \begin{command}{\overlay\marg{number}}
413 Shows the material till the end of the current \TeX\ group only on overlay numbered $\hbox{\meta{number}}+1$ or, if the |accumulated| option is given, from that overlay on. Usages of this command may be nested (as in \seminar). If an |\overlay| command is given inside another, it temporarily ``overrules'' the outer one as demonstrated in the following example, where it is assumed that the |accumulated| option is given.
414
415 \example
416 \begin{verbatim}
417 \begin{frame}
418 \begin{slide}
419 This is shown from the first slide on.
420 {\overlay{2}
421 This is shown from the third slide on.
422 {\overlay{1}
423 This is shown from the second slide on.
424 }
425 This is shown once more from the third slide on.
426 }
427 \end{slide}
428 \end{frame}
429 \end{verbatim}
430 \end{command}
431
432 \begin{environment}{{slide}\opt{|*|}}
433 Mainly installs an |\overlay{0}| around the \meta{environment contents}. If the |accumulated| option is given, this has no effect, but otherwise it will cause the main text of the slide to be shown \emph{only} on the first slide. This is useful if you really wish to physically place slides on top of each other.
434
435 The starred version does the same as the nonstarred one.
436
437 If this command is not issued inside a |\frame|, it sets up a frame with the |fragile=singleframe| option set. Thus, this frame will contain only a single slide.
438
439 \example
440 \begin{verbatim}
441 \begin{slide}
442 Some text.
443 \end{slide}
444
445 \frame{
446 \begin{slide}
447 Some text. And an {\overlay{1} overlay}.
448 \end{slide}
449 }
450 \end{verbatim}
451 \end{environment}
452
453 \begin{command}{\red}
454 Mapped to |\color{red}|.
455 \end{command}
456
457 \begin{command}{\blue}
458 Mapped to |\color{blue}|.
459 \end{command}
460
461 \begin{command}{\green}
462 Mapped to |\color{green}|.
463 \end{command}
464
465 \begin{command}{\ifslide}
466 True in the |presentation| modes, false in the |article| mode.
467 \end{command}
468
469 \begin{command}{\ifslidesonly}
470 Same as |\ifslide|.
471 \end{command}
472
473 \begin{command}{\ifarticle}
474 False in the |presentation| modes, true in the |article| mode.
475 \end{command}
476
477 \begin{command}{\ifportrait}
478 Always false.
479 \end{command}
480
481 The following commands are parsed by \beamer, but have no effect:
482 \begin{itemize}\itemsep=0pt\parskip=0pt
483 \item |\ptsize|.
484 \end{itemize}
485
486
487 \subsection{Foil\TeX}
488 \label{section-foiltex}
489
490 The package |beamerfoils| maps a subset of the commands of the \foils\ package to \beamer. Since this package defines only few non-standard \TeX\ commands and since \beamer\ implements all the standard commands, the emulation layer is pretty simple.
491
492 A copyright notice: The Foil\TeX\ package has a restricted license. For this reason, no example from the \foils\ package is included in the \beamer\ class. The emulation itself does not use the code of the \foils\ package (rather, it just maps \foils\ commands to \beamer\ commands). For this reason, our understanding is that the \emph{emulation} offered by the \beamer\ class is ``free'' and legally so. IBM has a copyright on the \foils\ class, not on the effect the commands of this class have. (At least, that's our understanding of things.)
493
494 The workflow for the migration is the following:
495 \begin{enumerate}
496 \item
497 Use the document class |beamer|, not |foils|.
498 \item
499 Add a |\usepackage{beamerfoils}| to start the emulation.
500 \item
501 Possibly add commands to install themes and templates.
502 \item
503 If the command |\foilhead| is used inside a |\frame| command or |frame| environment, it behaves like |\frametitle|. If it used outside a frame, it will start a new frame (with the |allowframebreaks| option, thus no overlays are allowed). This frame will persist till the next occurrence of |\foilhead| or of the new command |\endfoil|. Note that a |\frame| command will \emph{not} end a frame started using |\foilhead|.
504 \item
505 If you rely on automatic frame creation based on |\foilhead|, you will need to insert an |\endfoil| before the end of the document to end the last frame.
506 \item
507 If you use pdf\LaTeX\ to typeset the presentation, than you cannot include PostScript files. You should convert them to |.pdf| or to |.png| and adjust any usage of |\includegraphics| accordingly.
508 \item
509 Sizes of objects are different in \beamer, since the scaling is done by the viewer, not by the class. Thus a framebox of size 6 inches will be way too big in a \beamer\ presentation. You will have to manually adjust explicit dimension occurring in a foil\TeX\ presentation.
510 \end{enumerate}
511
512 \begin{package}{{beamerfoils}}
513 Include this package in a |beamer| presentation to get access to \foils\ commands. Use |beamer| as the document class, not |foils|.
514
515 \example
516 In the following example, frames are automatically created. The |\endfoil| at the end is needed to close the last frame.
517
518 \begin{verbatim}
519 \documentclass{beamer}
520 \usepackage{beamerfoils}
521
522 \begin{document}
523
524 \maketitle
525
526 \foilhead{First Frame}
527
528 This is on the first frame.
529 \pagebreak
530 This is on the second frame, which is a continuation of the first.
531
532 \foilhead{Third Frame}
533
534 This is on the third frame.
535
536 \endfoil
537 \end{document}
538 \end{verbatim}
539
540 \example
541 In this example, frames are manually inserted. No |\endfoil| is needed.
542
543 \begin{verbatim}
544 \documentclass{beamer}
545 \usepackage{beamerfoils}
546
547 \begin{document}
548
549 \frame{\maketitle}
550
551 \frame{
552 \foilhead{First Frame}
553 This is on the first frame.
554 }
555
556 \frame{
557 \foilhead{Second Frame}
558 This is on the second frame.
559 }
560 \end{document}
561 \end{verbatim}
562 \end{package}
563
564 In the following, the effects of \foils\ commands in \beamer\ are listed.
565
566 \begin{command}{\MyLogo\marg{logo text}}
567 This is mapped to |\logo|, though the logo is internally stored, such that it can be switched on and off using |\LogoOn| and |\LogoOff|.
568 \end{command}
569
570 \begin{command}{\LogoOn}
571 Makes the logo visible.
572 \end{command}
573
574 \begin{command}{\LogoOff}
575 Makes the logo invisible.
576 \end{command}
577
578 \begin{command}{\foilhead\oarg{dimension}\marg{frame title}}
579 If used inside a |\frame| command or |frame| environment, this is mapped to |\frametitle{|\meta{frame title}|}|. If used outside any frames, a new frame is started with the option |allowframebreaks|. If a frame was previously started using this command, it will be closed before the next frame is started. The \meta{dimension} is ignored.
580 \end{command}
581
582 \begin{command}{\rotatefoilhead\oarg{dimension}\marg{frame title}}
583 This command has exactly the same effect as |\foilhead|.
584 \end{command}
585
586 \begin{command}{\endfoil}
587 This is a command that is \emph{not} available in \foils. In \beamer, it can be used to end a frame that has automatically been opened using |\foildhead|. This command must be given before the end of the document if the last frame was opened using |\foildhead|.
588 \end{command}
589
590 \begin{environment}{{boldequation}\opt{|*|}}
591 This is mapped to the |equation| or the |equation*| environment, with |\boldmath| switched on.
592 \end{environment}
593
594 \begin{command}{\FoilTeX}
595 Typesets the foil\TeX\ name as in the \foils\ package.
596 \end{command}
597
598 \begin{command}{\bm\marg{text}}
599 Implemented as in the \foils\ package.
600 \end{command}
601
602 \begin{command}{\bmstyle\marg{text}\marg{more text}}
603 Implemented as in the \foils\ package.
604 \end{command}
605
606 The following additional theorem-like environments are predefined:
607 \begin{itemize}
608 \item |Theorem*|,
609 \item |Lemma*|,
610 \item |Corollary*|,
611 \item |Proposition*|, and
612 \item |Definition*|.
613 \end{itemize}
614 For example, the first is defined using |\newtheorem*{Theorem*}{Theorem}|.
615
616 The following commands are parsed by \beamer, but have no effect:
617 \begin{itemize}
618 \item |\leftheader|,
619 \item |\rightheader|,
620 \item |\leftfooter|,
621 \item |\rightfooter|,
622 \item |\Restriction|, and
623 \item |\marginpar|.
624 \end{itemize}
625
626
627 \subsection{\TeX Power}
628 \label{section-texpower}
629
630 The package |beamertexpower| maps a subset of the commands of the \texpower\ package, due to Stephan Lehmke, to \beamer. This subset is currently rather small, so a lot of adaptions may be necessary. Note that \texpower\ is not a full class by itself, but a package that needs another class, like |seminar| or |prosper| to do the actual typesetting. It may thus be necessary to additionally load an emulation layer for these also. Indeed, it \emph{might} be possible to directly use \texpower\ inside \beamer, but we have not tried that. Perhaps this will be possible in the future.
631
632 Currently, the package |beamertexpower| mostly just maps the |\stepwise| and related commands to appropriate \beamer\ commands. The |\pause| command need not be mapped since it is directly implemented by \beamer\ anyway.
633
634 The workflow for the migration is the following:
635 \begin{enumerate}
636 \item
637 Replace the document class by |beamer|. If the document class is |seminar| or |prosper|, you can use the above emulation layers, that is, you can include the files |beamerseminar| or |beamerprosper| to emulate the class.
638
639 All notes on what to do for the emulation of \seminar\ or \prosper\ also apply here.
640 \item
641 Additionally, add |\usepackage{beamertexpower}| to start the emulation.
642 \end{enumerate}
643
644 \begin{package}{{beamertexpower}}
645 Include this package in a |beamer| presentation to get access to the \texpower\ commands having to do with the |\stepwise| command.
646 \end{package}
647
648 A note on the |\pause| command: Both \beamer\ and \texpower\ implement this command and they have the same semantics; so there is no need to map this command to anything different in |beamertexpower|. However, a difference is that |\pause| can be used almost anywhere in \beamer, whereas it may only be used in non-nested situations in \texpower. Since \beamer\ is only more flexible than \texpower\ here, this will not cause problems when porting.
649
650 In the following, the effect of \texpower\ commands in \beamer\ are listed.
651
652 \begin{command}{\stepwise\marg{text}}
653 As in \texpower, this initiates text in which commands like |\step| or |\switch| may be given. Text contained in a |\step| command will be enclosed in an |\only| command with the overlay specification |<+(1)->|. This means that the text of the first |\step| is inserted from the second slide onward, the text of the second |\step| is inserted from the third slide onward, and so on.
654 \end{command}
655
656 \begin{command}{\parstepwise\marg{text}}
657 Same as |\stepwise|, only |\uncover| is used instead of |\only| when mapping the |\step| command.
658 \end{command}
659
660 \begin{command}{\liststepwise\marg{text}}
661 Same as |\stepwise|, only an invisible horizontal line is inserted before the \meta{text}. This is presumably useful for solving some problems related to vertical spacing in \texpower.
662 \end{command}
663
664 \begin{command}{\step\marg{text}}
665 This is either mapped to |\only<+(1)->|\meta{text} or to |\uncover<+(1)->|\meta{text}, depending on whether this command is used inside a |\stepwise| environment or inside a |\parstepwise| environment.
666 \end{command}
667
668 \begin{command}{\steponce\marg{text}}
669 This is either mapped to |\only<+(1)>|\meta{text} or to |\uncover<+(1)>|\meta{text}, depending on whether this command is used inside a |\stepwise| environment or inside a |\parstepwise| environment.
670 \end{command}
671
672 \begin{command}{\switch\marg{alternate text}\marg{text}}
673 This is mapped to |\alt<+(1)->{|\meta{text}|}{|\meta{alternate text}|}|. Note that the arguments are swapped.
674 \end{command}
675
676 \begin{command}{\bstep\marg{text}}
677 This is always mapped to |\uncover<+(1)->|\meta{text}.
678 \end{command}
679
680 \begin{command}{\dstep}
681 This just advances the counter |beamerpauses| by one. It has no other effect.
682 \end{command}
683
684 \begin{command}{\vstep}
685 Same as |\dstep|.
686 \end{command}
687
688 \begin{command}{\restep\marg{text}}
689 Same as |\step|, but the \meta{text} is shown on the same slide as the previous |\step| command. This is implemented by first decreasing the counter |beamerpauses| by one before calling |\step|.
690 \end{command}
691
692 \begin{command}{\reswitch\marg{alternate text}\meta{text}}
693 Like |\restep|, only for the |\switch| command.
694 \end{command}
695
696 \begin{command}{\rebstep\meta{text}}
697 Like |\restep|, only for the |\bstep| command.
698 \end{command}
699
700 \begin{command}{\redstep}
701 This command has no effect.
702 \end{command}
703
704 \begin{command}{\revstep}
705 This command has no effect.
706 \end{command}
707
708 \begin{command}{\boxedsteps}
709 Temporarily (for the current \TeX\ group) changes the effect of |\step| to issue an |\uncover|, even if used inside a |\stepwise| environment.
710 \end{command}
711
712 \begin{command}{\nonboxedsteps}
713 Temporarily (for the current \TeX\ group) changes the effect of |\step| to issue an |\only|, even if used inside a |\parstepwise| environment.
714 \end{command}
715
716 \begin{command}{\code\marg{text}}
717 Typesets the argument using a boldface typewriter font.
718 \end{command}
719
720 \begin{command}{\codeswitch}
721 Switches to a boldface typewriter font.
722 \end{command}