Progress on Figuro running with nimscripts! Thanks to @ElegantBeef's awesome nimscripter library. He's also made a cool nicoscript for live editing games. Cool stuff all around!
Here's a video if y'all like: <https://www.youtube.com/watch?v=bFHHa4hx9rg> The performance is better than I thought it'd be too. > About being composable and allowing users to utilize your library in > different ways (without starting library vs framework wars :), I think the > signal/slot idea that you want to adopt is on good track. It should be easy > for the user to define events/signals that their components could emit as well The ability for users to define events/signal is a big part of why signals/slots are great. They're clear, easy to document, and allow multiple subscribers. Also, QT makes use of them to enable parts of their GUI editors and such. You could in theory use a UI editor and just set the signals/slots back regular Nim code. > as completely replace that mechanism when they don't need it or when they > want to control things in their own way, in their own loop. It mostly falls > onto the API/DSL design to make the process as convenient and intuitive as > possible. I wouldn't be against being able to run with a custom event loop. In Figuro there's nothing in it's design that'd prevent it from doing that aside from figuring out APIs. Though I plan to make signal/slots core to the design to avoid confusion on how to do events. Thanks for the thoughts on the accessibility. It'd be fun to at least make a text based UI. Ugh, theming is a bit of a pain.
