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
Separate the JS player for local preview [feature request] #121
Comments
So my plan is to allow for replay in the terminal before uploading. We don't really need JavaScript player to do the preview. Would that work for you? |
Replaying in the terminal can solve the cases mentioned above (preview and presentation). Looking forward. It's still good to have the standalone JS player so that the presentation can be more integrated. When I make slides using HTML, e.g. using mdpress , I can directly embedded the demo as a page. |
+1 for this feature. Looking forward to it. Lemme see if I can help in some way. |
@hupili btw, you can already embed the demo in your slides. I did it here for example: http://krk-devops-docker.herokuapp.com/#/7 |
@sickill may I have a look at the source of that slides? It looks interesting. |
@hupili just open the source of the page and search for word "asciicast" - you'll find the embed scripts. |
Ability to record to local file, replay in terminal, edit and then upload has just been added. See 1.0 release post. |
I think it's a good feature to be able to view the recorded clips locally and decide whether to upload or not (or even better, modify before upload because I may have incidentally put my sensitive data on screen).
I already did some small modification of ascii.io-cli to allow choice of upload/ delete. When I come to this project, it's hard for me to separate the JS player out. I'm not familiar with RoR. It's hard for me to figure out how things are stitched together.
Another use case of the local JS player is for presentation without network connection. The quality of ascii.io demo is very high. I very much want to use it for next presentation.
The text was updated successfully, but these errors were encountered: