presently 0.14.1 → 0.15.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: de6eb2668cd67cd34eb8f02c51dce3bc3f823f71b8e553835d27c2476d3f793e
-  data.tar.gz: 37601886d71cc24f89510ed65d918dbb87bcd1de1d0c48718f96b15820790e23
+  metadata.gz: 42f99b653f49a0ac23d4c6b49314cde4ef814e70a7d274c7d67914e4f707514d
+  data.tar.gz: f308373c9741dad960682283d52df1d34e285e32e0c9155cd0911d3e62405562
 SHA512:
-  metadata.gz: 5d272168a8f3de208c69e56fb44083c2417987d5178afc6e021f9ae4c9c2ddd5985f3251637581e21aea109e9698778c147865baece48bd8a6cb7dd652c7c888
-  data.tar.gz: 1d30ea352a266fcf97def9fdba931adb9cec25933f74bebbac85ecb53e35ceaee46c2faebdcbde473bb853c2959e135a6a2b0b5309eaff91646a632f50ddc043
+  metadata.gz: 48116005297631e4fbdc4d06c1b83cfadb847d61dcb03ea60e603af4c28d9d0e678539fe114fbf6ce4f12e0fbc590281094e7fa40c2be003e9d488be31a25516
+  data.tar.gz: ed77bebb4005f828ab6b09c321cf075778a394706f0ff0bd6ffc2e2852e3c73ac2da3944e1ad7744cb82e3546702d0f81c4a966acc346f9c374b032f29100df9

data/bake/presently/export.rb

@@ -50,12 +50,15 @@ def pdf(output: "presentation.pdf", slides_root: "slides", notes: true, speaker:
 		begin
 			environment = Async::Service::Environment.build(
 				Presently::Environment::Application,
-				root: context.root,
-				slides_root: File.expand_path(slides_root, context.root),
+				root: Dir.pwd,
+				slides_root: slides_root,
 				endpoint: Async::HTTP::Endpoint.parse("http://localhost", bound_endpoint)
 			)
 			
-			evaluator = environment.evaluator
+			# PDF export always requires an HTTP server, regardless of the configured
+			# Lively transport:
+			transport = environment.with(environment.evaluator.http_environment)
+			evaluator = transport.evaluator
 			server = evaluator.make_server(evaluator.endpoint)
 			server_task = task.async{server.run}
 			

data/context/animating-slides.md

@@ -1,14 +1,6 @@
 # Animating Slides
 
-This guide explains how to animate content within slides using the `morph` transition and the slide scripting system.
-
-## How Morph Works
-
-The `morph` transition uses the browser's View Transitions API. When navigating between two slides, any element that has a `view-transition-name` style on both the old and new slide is matched — the browser captures its position and appearance in both states and animates between them.
-
-Elements without a matching name crossfade. The slide background stays completely still (no container animation).
-
-This is the mechanism that makes build sequences possible: the same element appears on consecutive slides with the same name, so it stays pinned in place while hidden elements appear around it.
+This guide explains how to animate content within slides using the slide scripting system.
 
 ## Slide Scripts
 
@@ -18,7 +10,6 @@ Any slide can include a JavaScript block at the end of its presenter notes secti
 ---
 template: default
 duration: 30
-transition: morph
 ---
 
 - First point
@@ -30,7 +21,7 @@ transition: morph
 Your presenter notes here.
 
 ```javascript
-slide.find("li").show(1, {group: "bullet"})
+slide.find("li").show(1)
 ```
 ~~~
 
@@ -52,7 +43,7 @@ slide.find(".callout")     // elements with a specific class
 
 ### `elements.show(n, options)`
 
-Shows the first `n` elements in the collection and hides the rest. Assigns `view-transition-name` to each element so the morph transition can match them across consecutive slides. Returns a `Promise` that resolves when any reveal animation completes.
+Shows the first `n` elements in the collection and hides the rest. Returns a `Promise` that resolves when any reveal animation completes.
 
 ``` javascript
 slide.find("li").show(0)  // all hidden
@@ -64,7 +55,6 @@ Options:
 
 | Option | Description |
 |---|---|
-| `group` | Name prefix for `view-transition-name` — must be consistent across slides for morph to match elements. Defaults to `"build"`. |
 | `effect` | Entry animation for the newly revealed element. See effects below. |
 
 ### `elements.builder(options)`
@@ -72,7 +62,7 @@ Options:
 Creates a `SlideBuilder` with default options and a cached position. Use this instead of calling `show()` manually when you want to reveal elements one at a time from a script.
 
 ``` javascript
-const bullets = slide.find("li").builder({group: "bullet", effect: "fly-up"})
+const bullets = slide.find("li").builder({effect: "fly-up"})
 bullets.show(0)       // hide all initially
 bullets.next()        // reveal first, plays fly-up
 bullets.next()        // reveal second, plays fly-up
@@ -115,7 +105,7 @@ A build sequence is a series of consecutive slides with the same content, each r
 ---
 template: default
 duration: 20
-transition: morph
+transition: fade
 ---
 
 - Real-time synchronization
@@ -127,7 +117,7 @@ transition: morph
 Let's walk through the key features.
 
 ```javascript
-slide.find("li").show(0, {group: "bullet"})
+slide.find("li").show(0)
 ```
 ~~~
 
@@ -136,7 +126,7 @@ slide.find("li").show(0, {group: "bullet"})
 ---
 template: default
 duration: 20
-transition: morph
+transition: fade
 ---
 
 - Real-time synchronization
@@ -148,12 +138,10 @@ transition: morph
 The display and presenter stay in sync over a WebSocket connection.
 
 ```javascript
-slide.find("li").show(1, {group: "bullet"})
+slide.find("li").show(1)
 ```
 ~~~
 
-The `group` option must be identical across all slides in the sequence so the browser matches the same elements. Without it, each slide uses the default `"build"` prefix — which is fine as long as only one build sequence is active per slide.
-
 Because all elements are in the DOM from the start (just hidden), the vertical layout stays consistent throughout the sequence — there is no shift as elements appear.
 
 ## Build Effects
@@ -161,7 +149,7 @@ Because all elements are in the DOM from the start (just hidden), the vertical l
 Pass an `effect` option to animate the newly revealed element as it appears. The effect plays as a CSS animation on the element and is removed automatically once it completes.
 
 ``` javascript
-slide.find("li").show(2, {group: "bullet", effect: "fly-up"})
+slide.find("li").show(2, {effect: "fly-up"})
 ```
 
 Available effects:
@@ -181,8 +169,8 @@ A slide can have multiple independent build groups. Each `find().show()` call is
 
 ``` javascript
 // Reveal list items as one group, callout div as another
-slide.find("li").show(3, {group: "bullet"})
-slide.find(".callout").show(1, {group: "callout", effect: "fly-up"})
+slide.find("li").show(3)
+slide.find(".callout").show(1, {effect: "fly-up"})
 ```
 
 ## In-Slide Animation with `slide.after()`
@@ -190,8 +178,8 @@ slide.find(".callout").show(1, {group: "callout", effect: "fly-up"})
 For sequential reveals within a single slide (without navigating to the next slide), use `slide.after()`. Each step fires a delay in milliseconds relative to the previous step. Returns a `SlideContext` so subsequent `.after()` calls chain naturally.
 
 ``` javascript
-const panes = slide.find(".pane").builder({group: "pane", effect: "fade"})
-const items = slide.find(".item").builder({group: "item", effect: "fly-up"})
+const panes = slide.find(".pane").builder({effect: "fade"})
+const items = slide.find(".item").builder({effect: "fly-up"})
 panes.show(0)
 items.show(0)
 

data/context/getting-started.md

@@ -263,9 +263,6 @@ Available transitions:
 | `fade` | Crossfade between slides |
 | `slide-left` | Current slide exits left, next enters from right |
 | `slide-right` | Current slide exits right, next enters from left |
-| `morph` | Matched elements animate between positions; everything else crossfades |
-
-The `morph` transition uses the browser's View Transitions API to smoothly animate individual elements between slides. Elements with the same `view-transition-name` across two consecutive slides are matched and interpolated.
 
 ## Presenter Notes
 

data/context/index.yaml

@@ -13,4 +13,4 @@ files:
 - path: animating-slides.md
   title: Animating Slides
   description: This guide explains how to animate content within slides using the
-    `morph` transition and the slide scripting system.
+    slide scripting system.

data/lib/presently/export.rb

@@ -20,8 +20,16 @@ module Presently
 		PageSize = Struct.new(:slide_width_px, :slide_height_px, :notes_height_px, keyword_init: true) do
 			PX_PER_CM = 96.0 / 2.54
 			
+			# Convert the slide width from CSS pixels to centimetres.
+			# @returns [Float] The slide width in centimetres.
 			def slide_width_cm  = (slide_width_px  / PX_PER_CM).round(4)
+			
+			# Convert the slide height from CSS pixels to centimetres.
+			# @returns [Float] The slide height in centimetres.
 			def slide_height_cm = (slide_height_px / PX_PER_CM).round(4)
+			
+			# Convert the notes panel height from CSS pixels to centimetres.
+			# @returns [Float] The notes panel height in centimetres.
 			def notes_height_cm = (notes_height_px / PX_PER_CM).round(4)
 		end
 		

data/lib/presently/slide.rb

@@ -249,7 +249,7 @@ module Presently
 		end
 		
 		# The transition type for animating into this slide.
-		# @returns [String | Nil] The transition name (e.g. `"fade"`, `"slide-left"`, `"morph"`), or `nil` for instant swap.
+		# @returns [String | Nil] The transition name (e.g. `"fade"`, `"slide-left"`, `"slide-right"`), or `nil` for instant swap.
 		def transition
 			@front_matter&.fetch("transition", nil)
 		end

data/lib/presently/version.rb

@@ -5,5 +5,5 @@
 
 # @namespace
 module Presently
-	VERSION = "0.14.1"
+	VERSION = "0.15.0"
 end

data/public/_static/index.css

@@ -364,18 +364,6 @@ html[data-transition="slide-right"]::view-transition-new(slide-container) {
 	animation: vt-slide-in-left 0.4s ease-in-out;
 }
 
-/* Magic move — the browser interpolates position/size for matched
-   view-transition-name elements. No cross-fade on the container
-   to avoid background dimming. */
-html[data-transition="morph"]::view-transition-old(slide-container) {
-	animation: none;
-	opacity: 0;
-}
-
-html[data-transition="morph"]::view-transition-new(slide-container) {
-	animation: none;
-}
-
 @keyframes vt-fade-out {
 	from { opacity: 1; }
 	to { opacity: 0; }
@@ -410,13 +398,6 @@ html[data-transition="morph"]::view-transition-new(slide-container) {
    BUILD EFFECTS
    ======================== */
 
-/* Suppress both pseudo-elements for hidden build elements so they
-   neither crossfade in nor crossfade out during the transition. */
-::view-transition-old(.build-hidden),
-::view-transition-new(.build-hidden) {
-	display: none;
-}
-
 /* Fade */
 .build-fade {
 	animation: vt-fade-in 0.4s ease;

data/public/slide.js

@@ -3,7 +3,6 @@
 // instead of tracking count manually. Created via SlideElements#builder(options).
 export class SlideBuilder {
 	#elements;
-	#prefix;
 	#defaultEffect;
 	#slide;
 	#step = 0;
@@ -11,7 +10,6 @@ export class SlideBuilder {
 	constructor(slide, elements, options = {}) {
 		this.#slide = slide;
 		this.#elements = elements;
-		this.#prefix = options.group || 'build';
 		this.#defaultEffect = options.effect || null;
 	}
 
@@ -26,16 +24,8 @@ export class SlideBuilder {
 		let revealedElement = null;
 
 		this.#elements.forEach((element, index) => {
-			// Only assign a group name if the element doesn't already have an explicit one.
-			// Preserving explicit names allows elements to participate in morph transitions
-			// to other slides while still being managed by the build system.
-			if (!element.style.viewTransitionName || element.style.viewTransitionName === 'none') {
-				element.style.viewTransitionName = `${this.#prefix}-${index + 1}`;
-			}
-
 			if (index < count) {
 				element.style.visibility = 'visible';
-				element.style.viewTransitionClass = '';
 
 				if (index === count - 1 && effect) {
 					element.classList.add(`build-${effect}`);
@@ -43,9 +33,6 @@ export class SlideBuilder {
 				}
 			} else {
 				element.style.visibility = 'hidden';
-				// Keep viewTransitionClass set so morph transitions can suppress
-				// crossfading on hidden elements when called inside startViewTransition.
-				element.style.viewTransitionClass = 'build-hidden';
 			}
 		});
 
@@ -75,11 +62,7 @@ export class SlideBuilder {
 		const effect = this.#slide.animated ? (overrides.effect !== undefined ? overrides.effect : this.#defaultEffect) : null;
 		const element = this.#elements[this.#step];
 
-		if (!element.style.viewTransitionName || element.style.viewTransitionName === 'none') {
-			element.style.viewTransitionName = `${this.#prefix}-${this.#step + 1}`;
-		}
 		element.style.visibility = 'visible';
-		element.style.viewTransitionClass = '';
 
 		this.#step += 1;
 
@@ -141,7 +124,6 @@ export class SlideElements {
 
 	// Create a stateful SlideBuilder for this element collection with default options.
 	// @parameter options [Object] Default options applied to every show() / next() call.
-	//   group: prefix for view-transition-name (default: "build")
 	//   effect: "fade", "fly-up", "fly-down", "fly-left", "fly-right", "scale"
 	// @returns [SlideBuilder]
 	builder(options = {}) {
@@ -152,7 +134,6 @@ export class SlideElements {
 	// Delegates to SlideBuilder for the actual implementation.
 	// @parameter count [Integer] Number of elements to show.
 	// @parameter options [Object]
-	//   group: prefix for view-transition-name (default: "build")
 	//   effect: "fade", "fly-up", "fly-down", "fly-left", "fly-right", "scale"
 	// @returns [Promise] Resolves when the animation completes (or immediately if no effect).
 	show(count, options = {}) {

data/readme.md

@@ -23,12 +23,19 @@ Please see the [project documentation](https://socketry.github.io/presently/) fo
 
   - [Getting Started](https://socketry.github.io/presently/guides/getting-started/index) - This guide explains how to use `presently` to create and deliver web-based presentations using Markdown slides.
 
-  - [Animating Slides](https://socketry.github.io/presently/guides/animating-slides/index) - This guide explains how to animate content within slides using the `morph` transition and the slide scripting system.
+  - [Animating Slides](https://socketry.github.io/presently/guides/animating-slides/index) - This guide explains how to animate content within slides using the slide scripting system.
 
 ## Releases
 
 Please see the [project releases](https://socketry.github.io/presently/releases/index) for all releases.
 
+### v0.15.0
+
+q
+
+  - Export works from current working directory.
+      - Remove explicit support for `morph` transition.
+
 ### v0.14.0
 
   - Increase code font size by 50%.
@@ -77,10 +84,6 @@ Please see the [project releases](https://socketry.github.io/presently/releases/
 
   - Add `bake presently:slides:speakers` task to print a timing breakdown grouped by speaker. Each speaker's slides are listed in presentation order with individual and total durations, making it easy to balance talk time in multi-speaker presentations. Slides without a `speaker` key are grouped under `(no speaker)`.
 
-### v0.5.0
-
-  - Add optional `speaker` front matter key to slides. When present, the current speaker's name is shown in the timing bar. If the next slide has a different speaker, a handoff indicator (e.g. `→ Next Speaker`) is shown alongside, giving presenters an at-a-glance cue for tag-team talks.
-
 ## See Also
 
   - [lively](https://github.com/socketry/lively) — The real-time application framework that powers Presently.

data/releases.md

@@ -1,5 +1,12 @@
 # Releases
 
+## v0.15.0
+
+q
+
+  - Export works from current working directory.
+      - Remove explicit support for `morph` transition.
+
 ## v0.14.0
 
   - Increase code font size by 50%.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: presently
 version: !ruby/object:Gem::Version
-  version: 0.14.1
+  version: 0.15.0
 platform: ruby
 authors:
 - Samuel Williams
@@ -44,14 +44,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.16'
+        version: '0.18'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.16'
+        version: '0.18'
 - !ruby/object:Gem::Dependency
   name: markly
   requirement: !ruby/object:Gem::Requirement
@@ -243,7 +243,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.6
+rubygems_version: 4.0.10
 specification_version: 4
 summary: A web-based presentation tool built with Lively.
 test_files: []