Open LiberalArtist opened 5 years ago
It has been a few years, and things are mostly still in the same state.
I haven't been motivated to improve on the state of the implementation here, because I just moved completely over to widescreen mode. It's nice that slides can be adaptive in principle, but I don't use that. Even when I run old talks, I normally want to modernize a detail or two, and it's easy to adjust to widescreen along the way. (Usually, it's a matter of improving a slide or two that looks needlessly crowded.)
The only thing I wonder is whether it would make sense to switch to widescreen as the default, instead of fullscreen. That way, I don't have to remember how to run slideshow --widescreen --save-aspect
when I set up a new machine, and the occasional new Slideshow user would not have to discover that approach. People who have fullscreen slides might need to run slideshow --fullscreen --save-aspect
after upgrading Racket, but hopefully that's fewer people than potential future users who want widescreen mode.
Currently, the only way to control the actual aspect ratio used for
#f
seems to be extra-linguistically, via theslideshow
executable.I think it would make sense for running a program in
#lang slideshow/widescreen
or#lang slideshow/fullscreen
directly viaracket
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.