An editor can be represented in a TUI but is not inherently a TUI-component; its implementation can be used across different user interfaces (although it is of course a stateful component for interactive editing such as in a UI).
For this purpose, I could (from limited consideration) envision a generic implementation separate from any individual component (such as the editor) which accounts for all components and computes at least the TUI layout for them.
I figure, that there is a lot of potential unification for UI building in this idea (controller.go is messy rn) but also something to really overcomplicate, so I'd like to leave it as an idea here and tackle it removed from any other feature-implementation.
An editor can be represented in a TUI but is not inherently a TUI-component; its implementation can be used across different user interfaces (although it is of course a stateful component for interactive editing such as in a UI).
For this purpose, I could (from limited consideration) envision a generic implementation separate from any individual component (such as the editor) which accounts for all components and computes at least the TUI layout for them.
I figure, that there is a lot of potential unification for UI building in this idea (
controller.gois messy rn) but also something to really overcomplicate, so I'd like to leave it as an idea here and tackle it removed from any other feature-implementation.