Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Smarter PDF export #29

Open
pepelsbey opened this issue Apr 6, 2019 · 3 comments
Open

Smarter PDF export #29

pepelsbey opened this issue Apr 6, 2019 · 3 comments
Labels
feature New feature or request

Comments

@pepelsbey
Copy link

pepelsbey commented Apr 6, 2019

Currently the only entry point for CLI is the index.html. In my case I often have multiple versions of my slides:

andersen.html
codefest.html
fwdays.html
yandex.html

It would be good if CLI could do the following:

  • Look for *.(html|htm) file in the root
  • If there’s only one found, just print PDF with the name of this file: index.pdf, not presentation.pdf like it does right now. You don’t expect presentation name because you don’t use it anywhere.
  • If there are multiple files, list all of them and ask which one to print, just like it does for the themes.

@nikolay-govorov what do you think?

@mrdimidium
Copy link

Hey. Sorry for the long answer.

Why such a hard workflow? Isn't it easier to count all /*.(htm|html) files of the presentation entry points? Then calling shower pdf will just turn all the entry points into PDF file.

@pepelsbey
Copy link
Author

pepelsbey commented May 2, 2019

When I run shower pdf I want to export a single file, not every HTML file available. There might be a demo file or something else. To be able to print exactly what I need, I’d love to see something like:

$ ls
$ foo.html bar.html
$ shower pdf foo.html 
>> foo.pdf
$ shower pdf
> foo.html
> bar.html ←
>> bar.pdf

shower pdf behavior would be similar to npm run one, where it lists all available options instead of running all of them.

@mrdimidium
Copy link

Sounds good, we'll do it

@mrdimidium mrdimidium added the feature New feature or request label May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants