Animation onclick - once only

[fyodr]

The animation ought to run only once after being clicked on. It now runs on an infinite loop after one click. This was great when we were just trying to get the thing to work, but it feels a little bit unpolished.

[bmccutchon]

We might consider displaying it in an HTML5 <video> tag instead of a canvas. This would allow the user to have video controls at the bottom (play/pause, volume, etc). If we go that route, this issue depends on #6 (or a generalized version of #6).

[fyodr]

If we use the server-generated version, then the server will have to generate every video the user watches. As I recall, we were minimizing server processing time by letting the user mess around on their own machine.

[bmccutchon]

Yes, but the same thing generated on the server could be generated on the client. The only reason we’re doing it on the server is because you can’t save things to disk from the client; downloads must come from the server.

On Sep 12, 2016, at 4:22 PM, fyodr notifications@github.com wrote:

If we use the server-generated version, then the server will have to generate every video the user watches. As I recall, we were minimizing server processing time by letting the user mess around on their own machine.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub #25 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AIRSTcVvZcuOxwWVUoXhbfNFZ0ewssIhks5qpcKygaJpZM4J7Cb-.

[fyodr]

Fair enough.

Still, implementing on the server and downloading can be handled without wiring it into current canvas - as well as vice versa. In the interest of minimizing labor, integrating these services should be a lower priority than achieving both.

[bmccutchon]

Um, actually, in the interests of minimizing labor, we shouldn’t write the same thing twice.

On Sep 12, 2016, at 4:34 PM, fyodr notifications@github.com wrote:

Fair enough.

Still, implementing on the server and downloading can be handled without wiring it into current canvas - as well as vice versa. In the interest of minimizing labor, integrating these services should be a lower priority than achieving both.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub #25 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AIRSTS_43ahRIjH1miEG-s7LOewBTzeIks5qpcV4gaJpZM4J7Cb-.

[fyodr]

I probably just have some bad assumptions about what is involved in the process.