Sudara
Sudara
Timothy from PlugData has graciously offered we steal their custom color picker so we can move away from JUCE's default one. https://github.com/plugdata-team/plugdata/blob/main/Source/Utility/ColourPicker.h 

This might not be trivial to fix, but would improve UX. So step 1 is to just investigate if a fix is possible, or a headache. Right now the interactive...
Right now children aren't shown because it doesn't match. This means if you want to drill down from the search, you'd have to cancel it out / makes workflow difficult...
Let's check out whether it's a need to force-set cache_classes when code isn't being changed between requests. Basically, is it a consistent amount of overhead? Widely variable?
I get a warning with this usage: ```cpp auto fadeOut = std::make_unique (friz::Parametric::CurveType::kEaseInQuartic, 0.0f, 1.0f, 0.5f * 60); auto animation = std::make_unique (friz::Animation::SourceList { std::move (fadeOut) }, 0); ``` ```...
Just to make this a formal feature request: I think it would be really sweet for clarity/readability if we added constructors that take ownership of incoming class objects. I'm usually...
 Would require passing in a gradient to render and compositing an RGBA image instead of single color.