Hey achempion, cheers 
it has been an on-and-off side-project for me for a while now, but about 5 months ago Scenic put out a new major release (v0.11-beta) and since then I have been working on it during all my spare-time coding hours. You managed to find a lot of bugs, I assure you there are even more of them you didn’t find I will get to work on fixing the one you reported (thankyou so much for this!).
It was awesome to watch your stream back and see someone in real-time interacting with software I wrote, really it was quite a thrill I will definitely check back in with you on twitch! I really like your project too, and as you saw I think we can have a lot of crossover - we have both implemented Buffer behaviours and I’m sure so much else.
Going forward, my main focus is to re-write from scratch the actual text_box component (which you found in neo_text_box.ex) and do it correctly, with new knowledge I’ve developed as I go about how to use Scenic correctly. This is a fairly complex problem when you have to implement it from scratch, and there are a few fairly distinct use-cases for one piece of code, e.g. I want to be able to support internal scrolling, resizing and wrapping of text, depending on opts that get passed in - I need to satisfy all these use cases in order to have one generic text-box component across the entire application, and it should become a re-usable component for the entire Scenic community. It should also support multi-mode (i.e. vim) editing, but that will probably come after/seperately.
Will keep you updated - keep streaming, I will check back in, and when I’ve fixed up some of these issues over the holidays maybe we can revisit it again, was super fun for me to watch you interact with Flamelex, I learned a lot and Flamelex will benefit a lot even just from users like you trying it out and sharing feedback! Let me know when you want someone to try out alice for the first time, I will gladly return the favor 
