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

Static mode #15

Open
sindresorhus opened this issue Jan 10, 2020 · 5 comments
Open

Static mode #15

sindresorhus opened this issue Jan 10, 2020 · 5 comments

Comments

@sindresorhus
Copy link
Owner

sindresorhus commented Jan 10, 2020

Some people have commented that this is wasteful. The reality is that it depends. You can load resource hungry websites or you can load simple static websites. Simple static websites take up very little CPU time.

However, I had this idea for people that just needs to show a static website. Instead of keeping the web view running the whole time, Plash could load the website in the web view, capture a screenshot, and then set the screenshot as the desktop view instead of the web view. That way it would look just as it would before, but it would be a static view of the web site. The reload interval would take care of keeping it up to date.

This would be opt-in.

Thoughts?

What should such an option be called?

@amitmerchant1990
Copy link

amitmerchant1990 commented Jan 10, 2020

What should such an option be called?

"Refresh Interval"?

@sindresorhus
Copy link
Owner Author

sindresorhus commented Jan 10, 2020

@amitmerchant1990 There's already is a "Reload Interval" option. The question is about what the static mode option should be called (including reasoning).

@amitmerchant1990
Copy link

amitmerchant1990 commented Jan 10, 2020

How about "Use as a Snapshot"? The word "snapshot" means impression of something at a point of time which I think is perfectly suitable for this particular feature. This, however, doesn't describe its changing behaviour on the interval. So, I'll leave it upto you.

@firrae
Copy link

firrae commented Jan 13, 2020

@sindresorhus could the screen shotting process not take up more CPU cycles making intermittent performance issues or is that fairly performant now?

@sindresorhus
Copy link
Owner Author

@firrae The screenshotting would happen only on the interval ticks, which is at maximum every second, but more often every minute, so it would be more efficient, yes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants