Slides

Calepin chunks work inside any Typst slide framework: the framework handles the presentation structure, while Calepin executes code and splices the results into the deck. This page shows small decks built with Mosaic and Touying.

Mosaic

Mosaic turns an ordinary Typst document into polished PDF slides: headings become slides, and everything can be styled with plain Typst. It ships with modern themes, ready-made layouts, nested grids, incremental reveals, speaker notes, and handouts.

Plain python and r fences are executable Calepin chunks, so a minimal Mosaic deck with live code looks like this:

#import "/.calepin/calepin.typ" as calepin
#import "@preview/mosaic:0.0.1" as m

#show: calepin.document

#show: m.setup.with(
  title: [_Calepin_: Code execution in Mosaic slides],
  authors: [Ada Lovelace],
)

#calepin.setup(
  echo: true,
  eval: true,
  results: "render",
)

#m.slide(layout: "title")

== Print from Python

```python
print("Hello, Mosaic!")
```

== Plot from R

```r
#| fig-width: 50%
#| fig-alt-text: Scatter plot of fuel efficiency against horsepower
plot(mpg ~ hp, data = mtcars)
```

Touying

This section shows a small Touying slide deck that uses Calepin chunks.

Touying handles the presentation structure: slides, themes, headings, and features such as #pause. Calepin handles code execution and stores chunk output so it can be shown later in the document.

The main interesting pattern here is delayed display. A chunk can run in one place with results: "hidden", and its saved output can be printed somewhere else with #calepin.results("label").

Example details:

Full slides.typ

#import "/.calepin/calepin.typ" as calepin
#import "@preview/touying:0.7.4": *
#import themes.simple: *

#show: calepin.document

#set document(title: [Calepin Touying slides])

#show: simple-theme.with(aspect-ratio: "16-9")

#show raw.where(block: true): set text(size: .8em)

#title-slide[
  #calepin.setup(
    echo: true,
    eval: true,
    results: "render",
  )
  _Calepin_: Code execution in Touying slides
]

== Print from Python

```python
print("Hello, Touying!")
```

== Plot from R

```r
#| fig-width: 50%
#| fig-alt-text: Scatter plot of fuel efficiency against horsepower
plot(mpg ~ hp, data = mtcars)
```

== Compute in one column; show in another

Use the `results: "hidden"` option to keep the output hidden from the code location, then call it later with `calepin.results(label)` in the other column.

#grid(columns: (1fr, 1fr), gutter: .4em, [
=== Column 1: Code here
#calepin.chunk("python", label: "summary2", results: "hidden")[
```python
values = [2, 3, 5, 8, 13]
total = sum(values)
print(f"Total = {total}")
```
]
],

[
=== Column 2: Output here
#calepin.results("summary2")
],
)

== Compute in one slide; show in another

#calepin.chunk("python", label: "next-slide-claim", results: "hidden")[
```python
baseline = 120
current = 156
change = (current - baseline) / baseline
print(f"Change from baseline: {change:.0%}")
```
]

The chunk source is visible here, but `results: "hidden"` keeps its output off
this slide.

== Result on the next slide

#calepin.results("next-slide-claim")

The same label can be reused multiple times, anywhere in the deck.

#calepin.results("next-slide-claim")

Rendered PDF