Feature request: preview only current slide?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
Research direction
Start with the VS Code plugin's preview workflow and the distinction between preview and render described in the issue. Determine how slide selection is handled, then define and test a configurable choice between the current slide, adjacent slides, and the whole presentation; done means previewing avoids rendering unrelated slides while full render remains available.
Written by the indexing model from the issue text.
Description
When preparing a presentation, a simple (and, I assume, rather typical) workflow would be something like:
1- Edit a slide
2- Test (ie preview its animations, check errors, layout, etc.)
3- Go to the next/previous slide, to check the transitions
4- Advance to a new slide and start again at 1-
When the presentation has several slides (eg. 70), the preview becomes a real bottleneck in terms of time because in order to see the current slide you ask quarto to render all the presentation. (here I am assuming that the time it takes to render a presentation of 87 slides is much longer than the time it takes to render 1-3 slides, and the more slides the longer it takes. If this assumption is wrong then this message can be disregarded).
Also, when you have already finished all the previous slides, you normally don't really intend to see them again every time you save (to inspect the current slide). Therefore it would help a lot if the user could chose if she/he wants to render only the current slide or the whole presentation*
Is there a way to configure the VSC plugin to only render the current (or say, the previous + the current + the next) slide only?
If not, would it make sense to turn this into a feature request?
- Actually, since
previewis named as just a preview, I would expect that it shows only what you're doing now and it's optimized for speed (ideally, real-time). And letrenderdo the more serious, complete job.
Thanks so much for this great software.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from quarto-dev/quarto
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
quarto-dev/quarto#1099 ·
-
vscode
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
quarto-dev/quarto#934 · 1 comment · 2 reactions ·
-
vscode
Difficulty 5/5 Over a week Newbie friendliness 42/100
quarto-dev/quarto#1130 ·
-
vscode
Difficulty 3/5 1-2 days Newbie friendliness 68/100
quarto-dev/quarto#1122 ·
-
bug vscode zotero
Difficulty 4/5 3-5 days Newbie friendliness 48/100
quarto-dev/quarto#1119 · 1 comment ·
All issues in quarto-dev/quarto
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area:tools bug good first issue help wanted priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
TaewoooPark/Motifcode#14 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
newrelic-experimental/preflight#793 · 1 comment ·
-
bug 🐞
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#15320 ·