racket / racket/slideshow

Running slideshow/widescreen and slideshow/fullscreen modules directly

Open
#19 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
38
Forks
20
PR merge metrics
No merged PRs in 30d

Description

Currently, the only way to control the actual aspect ratio used for #f seems to be extra-linguistically, via the slideshow executable.

I think it would make sense for running a program in #lang slideshow/widescreen or #lang slideshow/fullscreen directly via racket or DrRacket to set the default aspect ratio accordingly. In particular, when using DrRacket to run a module in #lang slideshow/widescreen that incorporates a library slide function with an adaptive aspect ratio, the library slide will currently be in full-screen, which I found surprising.

It might also make sense for running the slideshow executable without an explicit --widescreen or --fullscreen argument to similarly let #lang slideshow/widescreen and #lang slideshow/fullscreen establish the default aspect ratio, though that seems like it would be more complicated to implement.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing how #lang slideshow/widescreen and #lang slideshow/fullscreen behave when run via racket or DrRacket, especially for adaptive aspect-ratio slide functions. Then inspect the slideshow executable's --widescreen and --fullscreen entry points. Done means the language modules establish the expected default aspect ratio when run directly, with the executable behavior clarified or updated as appropriate.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.