I’m starting work on a mid/large sized audio app for my final-final university project, and plan to use a giant
ValueTree as my model/controller to store the entire app state and generate the view (as detailed in the talk).
My big question is, how does
ComponentBuilder fit into the realm of the talk? It seems like it does a lot of the same things as the
ValueTreeItem class in the talk’s example code, with slightly less control since it doesn’t use direct
ValueTree::Listener callbacks, instead using the
Any enlightenment on how these pieces fit together or a more concrete example of when to use and when not to use
ComponentBuilder would be much appreciated.
EDIT: Doh, just ran across Is anyone using the ComponentBuilder class?
Guess I’ll make my own
ValueTree management classes then - which makes sense I suppose because not every
ValueTree backed thing will necessarily be a
Component - sometimes you just want a
ValueTree backed object for interfacing with the