Nate This is amazing to see and is precisely what I've dreamed about having! Super exciting! Is there any chance that this even in the super early phases will be included in the 4.3(.15)-beta?
Either way, keep up the great work! This update is proving to be absolutely incredible!
Additionally, I'm well aware that the runtime itself is open source but it'd be amazing if there were a way for me to contribute to the development of the editor as well! I'd love to help you guys out in any way and improve this fantastic platform. Has that ever been considered?
Not suggesting that it should be under a full 'Open Source' i.e. OSI license, but with clearly defined protections and boundaries similar to those defined in the runtime such that others could aid in the development process without compromising the business model. I'm sure I'm not alone in that I'd absolutely love the opportunity be more hands-on and actually contribute directly with e.g. fixing up bugs or even starting on initial implementations of workflows such as this or other ideas without taking capacity away from the team. This could additionally bridge a gap allowing projects to extend the runtime with project-specific needs ahead of e.g. a plugin ecosystem or something.
Just thought I'd share some thoughts 🙂