beamerpkg 1.0.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- beamerpkg-1.0.1/LICENSE +176 -0
- beamerpkg-1.0.1/PKG-INFO +281 -0
- beamerpkg-1.0.1/README.md +260 -0
- beamerpkg-1.0.1/pyproject.toml +39 -0
- beamerpkg-1.0.1/src/beamerpkg/__init__.py +5 -0
- beamerpkg-1.0.1/src/beamerpkg/cli.py +170 -0
- beamerpkg-1.0.1/src/beamerpkg/package.py +418 -0
- beamerpkg-1.0.1/src/beamerpkg/pdf_media.py +94 -0
- beamerpkg-1.0.1/src/beamerpkg/tex/beamerpkg.sty +29 -0
beamerpkg-1.0.1/LICENSE
ADDED
|
@@ -0,0 +1,176 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
beamerpkg-1.0.1/PKG-INFO
ADDED
|
@@ -0,0 +1,281 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: beamerpkg
|
|
3
|
+
Version: 1.0.1
|
|
4
|
+
Summary: Portable Beamer/PDF presentation bundles with external media assets
|
|
5
|
+
License-Expression: Apache-2.0
|
|
6
|
+
License-File: LICENSE
|
|
7
|
+
Author: Uli Kerzel
|
|
8
|
+
Requires-Python: >=3.11,<4.0
|
|
9
|
+
Classifier: Programming Language :: Python :: 3
|
|
10
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
11
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
12
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
13
|
+
Classifier: Programming Language :: Python :: 3.14
|
|
14
|
+
Classifier: Programming Language :: Python :: 3.15
|
|
15
|
+
Requires-Dist: pypdf (>=5.0,<7.0)
|
|
16
|
+
Project-URL: Homepage, https://github.com/ukerzel/beamerpkg
|
|
17
|
+
Project-URL: Issues, https://github.com/ukerzel/beamerpkg/issues
|
|
18
|
+
Project-URL: Repository, https://github.com/ukerzel/beamerpkg
|
|
19
|
+
Description-Content-Type: text/markdown
|
|
20
|
+
|
|
21
|
+
# beamerpkg
|
|
22
|
+
|
|
23
|
+
`beamerpkg` makes multimedia Beamer presentations portable without replacing
|
|
24
|
+
Beamer's rendering model.
|
|
25
|
+
|
|
26
|
+
```text
|
|
27
|
+
Beamer -> ordinary PDF + external MP4 files -> one relocatable .beamerpkg
|
|
28
|
+
|
|
|
29
|
+
v
|
|
30
|
+
unpack temporarily + pdfpc
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
Equations, TikZ, columns, backgrounds, arrows, Beamer overlays, fonts, and all
|
|
34
|
+
other slide layout remain PDF. The package layer only restores external media at
|
|
35
|
+
the relative paths already referenced by the PDF.
|
|
36
|
+
|
|
37
|
+
## Status
|
|
38
|
+
|
|
39
|
+
The container/path MVP was validated on **2026-09-30** with pdfpc under WSL/WSLg:
|
|
40
|
+
the packaged PDF rendered normally and the packaged H.264 video played in the
|
|
41
|
+
TeX-defined rectangle. The full-resolution autoplay demo also works.
|
|
42
|
+
|
|
43
|
+
Version 0.2 adds **wrapperless media discovery**: for standard Beamer
|
|
44
|
+
`multimedia/\movie` documents, `beamerpkg pack` reads the PDF annotation and
|
|
45
|
+
collects the referenced local media automatically. A `.beamerpkg-assets`
|
|
46
|
+
sidecar is no longer required for normal use.
|
|
47
|
+
|
|
48
|
+
## Package format
|
|
49
|
+
|
|
50
|
+
A `.beamerpkg` is an ordinary ZIP archive:
|
|
51
|
+
|
|
52
|
+
```text
|
|
53
|
+
talk.beamerpkg
|
|
54
|
+
├── manifest.json
|
|
55
|
+
├── talk.pdf
|
|
56
|
+
├── talk.pdfpc # optional
|
|
57
|
+
├── media/
|
|
58
|
+
│ └── simulation.mp4
|
|
59
|
+
└── source/ # optional editable source snapshot
|
|
60
|
+
├── talk.tex
|
|
61
|
+
├── figures/
|
|
62
|
+
└── references.bib
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
The manifest contains SHA-256 hashes and byte sizes. Runtime media are stored at
|
|
66
|
+
exactly the same relative paths used by Beamer. Optional editable sources live
|
|
67
|
+
under `source/` and are recorded separately in the manifest.
|
|
68
|
+
|
|
69
|
+
## Install for development
|
|
70
|
+
|
|
71
|
+
Requires Python 3.11+ and Poetry.
|
|
72
|
+
|
|
73
|
+
```bash
|
|
74
|
+
poetry install
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
The only runtime Python dependency is `pypdf`, used to inspect PDF annotations.
|
|
78
|
+
|
|
79
|
+
## Optional editable source payload
|
|
80
|
+
|
|
81
|
+
A presentation package can also carry the LaTeX source and authoring assets so
|
|
82
|
+
the recipient can modify and rebuild the presentation without editing the PDF.
|
|
83
|
+
|
|
84
|
+
Source inclusion is explicit. Pass a source root and repeat `--source` for the
|
|
85
|
+
files or directories to preserve:
|
|
86
|
+
|
|
87
|
+
```bash
|
|
88
|
+
poetry run beamerpkg pack build/talk.pdf \
|
|
89
|
+
--root build \
|
|
90
|
+
--source-root . \
|
|
91
|
+
--source talk.tex \
|
|
92
|
+
--source figures \
|
|
93
|
+
--source references.bib
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
Those files are stored with their relative structure under `source/`:
|
|
97
|
+
|
|
98
|
+
```text
|
|
99
|
+
source/
|
|
100
|
+
├── talk.tex
|
|
101
|
+
├── figures/
|
|
102
|
+
│ └── plot.png
|
|
103
|
+
└── references.bib
|
|
104
|
+
```
|
|
105
|
+
|
|
106
|
+
Because `.beamerpkg` is an ordinary ZIP archive, a recipient can unpack it,
|
|
107
|
+
edit the source tree, and rebuild with their normal LaTeX toolchain. Runtime
|
|
108
|
+
presentation files remain separate, so including sources never changes pdfpc
|
|
109
|
+
playback.
|
|
110
|
+
|
|
111
|
+
The source snapshot is deliberately opt-in and explicit: beamerpkg does not
|
|
112
|
+
guess which files constitute a reproducible authoring project. Directories are
|
|
113
|
+
included recursively; source paths must remain within `--source-root`, and
|
|
114
|
+
symlinks are rejected.
|
|
115
|
+
|
|
116
|
+
An asset needed both by the runtime presentation and by the editable source tree
|
|
117
|
+
may be stored twice. This keeps both trees self-contained and avoids symlink or
|
|
118
|
+
viewer-specific deduplication behavior in the package format.
|
|
119
|
+
|
|
120
|
+
## Standard Beamer: no Beamerpkg LaTeX helper required
|
|
121
|
+
|
|
122
|
+
The wrapperless standard-Beamer route is **click-to-start in pdfpc**. This is
|
|
123
|
+
the expected behavior of the normal `\movie` annotation path; autoplay is a
|
|
124
|
+
separate pdfpc-specific feature described below.
|
|
125
|
+
|
|
126
|
+
Write an ordinary Beamer movie:
|
|
127
|
+
|
|
128
|
+
```latex
|
|
129
|
+
\usepackage{multimedia}
|
|
130
|
+
|
|
131
|
+
\movie[loop,showcontrols]
|
|
132
|
+
{\includegraphics[width=\linewidth]{media/poster.png}}
|
|
133
|
+
{media/video.mp4}
|
|
134
|
+
```
|
|
135
|
+
|
|
136
|
+
Compile it normally, then package it:
|
|
137
|
+
|
|
138
|
+
```bash
|
|
139
|
+
poetry run beamerpkg pack talk.pdf --root .
|
|
140
|
+
```
|
|
141
|
+
|
|
142
|
+
The packer discovers the external `/Movie` file reference from the PDF,
|
|
143
|
+
validates that it is a safe local relative path, and includes it at the same path
|
|
144
|
+
inside the container.
|
|
145
|
+
|
|
146
|
+
An explicit sidecar remains available as a compatibility/fallback route:
|
|
147
|
+
|
|
148
|
+
```bash
|
|
149
|
+
poetry run beamerpkg pack talk.pdf --root . --assets talk.beamerpkg-assets
|
|
150
|
+
```
|
|
151
|
+
|
|
152
|
+
## pdfpc autoplay
|
|
153
|
+
|
|
154
|
+
Autoplay is viewer-specific rather than part of the container format. For pdfpc,
|
|
155
|
+
the bundled LaTeX helper `beamerpkg.sty` provides:
|
|
156
|
+
|
|
157
|
+
```latex
|
|
158
|
+
\pkgpdfpcmovie[autostart&loop]
|
|
159
|
+
{\includegraphics[width=\linewidth]{media/poster.png}}
|
|
160
|
+
{media/video.mp4}
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
The helper ships with the Python package. `beamerpkg texdir` prints its
|
|
164
|
+
directory, so LaTeX can find it without copying files:
|
|
165
|
+
|
|
166
|
+
```bash
|
|
167
|
+
TEXINPUTS="$(beamerpkg texdir)//:" pdflatex talk.tex
|
|
168
|
+
```
|
|
169
|
+
|
|
170
|
+
In a repository checkout it lives at `src/beamerpkg/tex/beamerpkg.sty`.
|
|
171
|
+
|
|
172
|
+
This emits pdfpc's `run:` launch-link mechanism. The packer also recognizes
|
|
173
|
+
these pdfpc media launch links and strips their query options when collecting
|
|
174
|
+
the underlying media file.
|
|
175
|
+
|
|
176
|
+
## pdfpc speaker notes and settings
|
|
177
|
+
|
|
178
|
+
If a same-name pdfpc sidecar exists beside the PDF, it is included automatically:
|
|
179
|
+
|
|
180
|
+
```text
|
|
181
|
+
talk.pdf
|
|
182
|
+
talk.pdfpc
|
|
183
|
+
```
|
|
184
|
+
|
|
185
|
+
```bash
|
|
186
|
+
poetry run beamerpkg pack talk.pdf --root .
|
|
187
|
+
```
|
|
188
|
+
|
|
189
|
+
The resulting package records `talk.pdfpc` separately as `notes` in the
|
|
190
|
+
manifest and restores it beside `talk.pdf` before launching pdfpc. This keeps
|
|
191
|
+
speaker notes and other pdfpc presentation metadata portable without putting
|
|
192
|
+
them into the PDF itself.
|
|
193
|
+
|
|
194
|
+
The repository demo contains `examples/demo.pdfpc` with a visible speaker note
|
|
195
|
+
on the first page so this behavior can be checked in presenter view.
|
|
196
|
+
|
|
197
|
+
## Inspect and present
|
|
198
|
+
|
|
199
|
+
```bash
|
|
200
|
+
poetry run beamerpkg inspect talk.beamerpkg
|
|
201
|
+
poetry run beamerpkg present talk.beamerpkg
|
|
202
|
+
```
|
|
203
|
+
|
|
204
|
+
`beamerpkg present` validates the archive, extracts it to a temporary directory
|
|
205
|
+
while preserving all relative paths, launches `pdfpc` from that directory, and
|
|
206
|
+
keeps the directory alive until the presenter exits. Arguments after `--` are
|
|
207
|
+
forwarded verbatim to the presenter before the PDF filename.
|
|
208
|
+
|
|
209
|
+
For a single physical monitor, keep both pdfpc windows available and switch
|
|
210
|
+
between presenter and audience views with the desktop window switcher.
|
|
211
|
+
|
|
212
|
+
When invoking through Poetry, pass pdfpc options directly after the package:
|
|
213
|
+
|
|
214
|
+
```bash
|
|
215
|
+
poetry run beamerpkg present talk.beamerpkg -w both
|
|
216
|
+
```
|
|
217
|
+
|
|
218
|
+
Poetry may consume a literal `--` separator before the Beamerpkg CLI sees it.
|
|
219
|
+
When invoking an installed `beamerpkg` executable directly, the explicit
|
|
220
|
+
separator form is also supported:
|
|
221
|
+
|
|
222
|
+
```bash
|
|
223
|
+
beamerpkg present talk.beamerpkg -- -w both
|
|
224
|
+
```
|
|
225
|
+
|
|
226
|
+
This is intentionally transparent passthrough rather than a Beamerpkg-specific
|
|
227
|
+
single-monitor mode. Other pdfpc options work the same way.
|
|
228
|
+
|
|
229
|
+
## Demo
|
|
230
|
+
|
|
231
|
+
The demo uses the full repository assets, a pdfpc metadata sidecar, and an
|
|
232
|
+
editable source snapshot:
|
|
233
|
+
|
|
234
|
+
- `examples/media/gemini_generated_video_b2693757.mp4`
|
|
235
|
+
- `examples/media/video-poster_big.png`
|
|
236
|
+
- `examples/demo.pdfpc` (speaker notes / pdfpc metadata)
|
|
237
|
+
- `source/examples/demo.tex`
|
|
238
|
+
- `source/examples/media/...`
|
|
239
|
+
- `source/src/beamerpkg/tex/beamerpkg.sty`
|
|
240
|
+
|
|
241
|
+
The mixed demo also contains two lightweight Beamer/PDF motion examples before
|
|
242
|
+
the video slides:
|
|
243
|
+
|
|
244
|
+
- a short `\transfade[duration=0.2]` page transition;
|
|
245
|
+
- a three-state manual overlay sequence that progressively builds
|
|
246
|
+
`Input -> Model -> Result` and remains fully reversible with the arrow keys.
|
|
247
|
+
|
|
248
|
+
Both are encoded in the PDF itself; `beamerpkg` does not need to discover or
|
|
249
|
+
package anything special for them. The overlay example deliberately avoids
|
|
250
|
+
`\transduration`: timed PDF pages restart their timer when revisited, which
|
|
251
|
+
makes backward navigation jump forward again.
|
|
252
|
+
|
|
253
|
+
Build both the mixed autoplay demo and a pure stock-Beamer wrapperless example:
|
|
254
|
+
|
|
255
|
+
```bash
|
|
256
|
+
git pull --rebase
|
|
257
|
+
poetry install
|
|
258
|
+
./examples/build_demo.sh
|
|
259
|
+
|
|
260
|
+
poetry run beamerpkg present examples/demo.beamerpkg
|
|
261
|
+
poetry run beamerpkg present examples/wrapperless.beamerpkg
|
|
262
|
+
```
|
|
263
|
+
|
|
264
|
+
`examples/demo.tex` also embeds speaker notes and a 10-minute countdown via
|
|
265
|
+
the standard `pdfpc` LaTeX package, so they travel inside the PDF itself. The
|
|
266
|
+
title page deliberately has no embedded note: pdfpc lets an embedded note
|
|
267
|
+
replace the sidecar note for the same page, so page 1 keeps showing the
|
|
268
|
+
`examples/demo.pdfpc` note and both routes can be checked in presenter view.
|
|
269
|
+
|
|
270
|
+
`examples/wrapperless.tex` imports only Beamer's `multimedia` package. It is
|
|
271
|
+
the integration proof that packaging no longer depends on a Beamerpkg-specific
|
|
272
|
+
LaTeX command. In pdfpc this wrapperless example is click-to-start.
|
|
273
|
+
|
|
274
|
+
The mixed `examples/demo.tex` intentionally contains two video slides: one
|
|
275
|
+
standard wrapperless `\movie` slide that is click-to-start, followed by one
|
|
276
|
+
pdfpc-specific `\pkgpdfpcmovie[autostart&loop]` slide that starts
|
|
277
|
+
automatically.
|
|
278
|
+
|
|
279
|
+
See [`docs/MVP.md`](https://github.com/ukerzel/beamerpkg/blob/main/docs/MVP.md) for the original acceptance test and
|
|
280
|
+
[`docs/NEXT_STEPS.md`](https://github.com/ukerzel/beamerpkg/blob/main/docs/NEXT_STEPS.md) for the remaining work.
|
|
281
|
+
|