Mooflod widgets should be designed with scalability in mind. Currently, too many values (e.g. labels, instruments, parameters) are hardcoded or rely on magic numbers and strings. This makes it difficult to adapt the widgets for different use cases or integrate them into other systems.
-
We should refactor the implementation to allow:
-
Easy configuration of labels, instruments, and visual representation.
-
Avoidance of hardcoded values; use named constants or external configuration instead.
-
A more declarative or data-driven approach to define widget behavior.
-
This will make Mooflod more modular, reusable, and user-friendly — especially for live coding and UI composition.
Mooflod widgets should be designed with scalability in mind. Currently, too many values (e.g. labels, instruments, parameters) are hardcoded or rely on magic numbers and strings. This makes it difficult to adapt the widgets for different use cases or integrate them into other systems.
We should refactor the implementation to allow:
Easy configuration of labels, instruments, and visual representation.
Avoidance of hardcoded values; use named constants or external configuration instead.
A more declarative or data-driven approach to define widget behavior.
This will make Mooflod more modular, reusable, and user-friendly — especially for live coding and UI composition.