W3C home > Mailing lists > Public > public-device-apis-log@w3.org > April 2021

[system-wake-lock] Use case: Simulations, rendering and creative coding (#7)

From: Jaume Sanchez via GitHub <sysbot+gh@w3.org>
Date: Fri, 09 Apr 2021 11:34:36 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-854440239-1617968074-sysbot+gh@w3.org>
spite has just created a new issue for https://github.com/w3c/system-wake-lock:

== Use case: Simulations, rendering and creative coding ==
I know it's a fringe use case of the web, but some of us do creative coding in the browser. Some of the algorithms are iterative in nature, and take some time to stabilise, accumulate, resolve, etc., besides the rendering: physics simulations, flow fields tracing, growth algorithms and more.

It's usually left to a .`step()` or `.simulate()` function that gets called with `requestAnimationFrame` until all works is done. It may or may not render to screen. 

With throttling now applied to Chrome, for instance, it becomes a dedicated task to keep the tab active and visible so the process goes on, even if running on a computer not running on battery.

Please view or discuss this issue at https://github.com/w3c/system-wake-lock/issues/7 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 April 2021 11:34:38 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:58 UTC