I’m working on a new way of writing “dense” UI inspired by MVVM + ECS, and this is the debugger for the “View Model Components” (VMCs?) in the UI The problem I’m usually facing with my apps is that we aim to pack many many features into small areas (for example: context menus, keyboard shortcuts, focus management, spatial navigation, version control diff presentation, multiplayer user presence, and then the parts that are unique to your app). My goal in managing this complexity is to be able to write each individual part of the application in its own single file. All things related to “module” editing, diffing, keyboard shortcuts, spatial navigation, CRDT sync, etc should be in a single file. Then, each shared behavior’s logic are implemented in their own single files. This is what is best as well for LLMs to understand and build out features without needing to understand everything all at once. Here, I’ve taken a video of just the “debugger” I developed in the last two days to observe the state of all these components for each item in the world.

nice! are you presenting it in the next FoC virtual meetup? 🙂

Hmm last time I had shown the prompt editor, I had some really great feedback that I should somehow demonstrate the development cycle using the dev tool so I kinda wanna think about how I can demonstrate that with this

Custom debuggers for the win :)