You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, in many browsers, students can already right-click on a drawing in the CodeWorld canvas, and save it as an image. That's great, but it's not very discoverable, and the steps to do it depend on the browser. We would like to make export to images a built-in capability of CodeWorld.
It's not possible today to export an animation in a common format. Students should be able to easily save their animations as either animated gif files, or as videos. It should be easy to upload them to YouTube, Facebook, or Instagram.
It's possible to consider the same thing for simulations; though, because simulations get random number sources, it's not entirely semantically sound. That is, you'd be better off labeling this as "record" rather than "export". Similarly, you could offer to "record" an interaction, as well.
It supports exports to WebM and GIF. We could add start and stop recording buttons for stuff like simulations. WebM exporting is only on Chrome though. GIF support seems to be universal.
Today, in many browsers, students can already right-click on a drawing in the CodeWorld canvas, and save it as an image. That's great, but it's not very discoverable, and the steps to do it depend on the browser. We would like to make export to images a built-in capability of CodeWorld.
It's not possible today to export an animation in a common format. Students should be able to easily save their animations as either animated gif files, or as videos. It should be easy to upload them to YouTube, Facebook, or Instagram.
It's possible to consider the same thing for simulations; though, because simulations get random number sources, it's not entirely semantically sound. That is, you'd be better off labeling this as "record" rather than "export". Similarly, you could offer to "record" an interaction, as well.
Related: #22
The text was updated successfully, but these errors were encountered: