Closed w0rd-driven closed 1 year ago
There's no useful frontend event so keeping the same speak
event is fine for now.
This is rough as I don't quite know all the ins and outs of what I copy pasted into place but I'm getting there. The interactions between the front and backend are a little odd to pick up at first.
Adding interaction buttons will be saved for later if implemented at all. I don't quite know how all of this will play together. I could see a potential future where the editor is replaced as it doesn't need syntax highlighting. I thought maybe I could get the voices to use inflection but I doubt it. For the broadest compatibility, it could be useful to bring in easy-speech but that could be a very heavy-handed dependency if it worked.
Replace the existing functionality with a Vue3 scaffold taken from many examples like kino_db or kino_explorer.
%Kino.Markdown{content}
section. We just need a change event on the front end that triggersupdate_text
.We'll create a companion Livebook to work through what the final version should be. I wanted to keep the initial draft though I could've really benefitted from source control on day zero.
The companion Livebook should have a basic interview conversation between multiple voices in various configurations.