The look and feel workflow in JUCE has come out of style for all use cases except where it is necessary to change the design language around a lot. For all other purposes it leads to extremely verbose and overly encumbered implementations.
The more modern way would be to use custom components that incorporate the style/design in their implementation. AmbiCreator and StereoCreator already use this approach, so it would be synergetic to use it in PolarDesigner as well.
Additionally, the way LaF is implemented right now breaks a lot of the encapsulation that makes it useful in the first place (layout/placement code in LaF, etc.).
If the plugin is ever refactored to get rid of 3rd party GPLv3 licensed code, this would be a perfect time to tackle retiring the custom LaF as well.
The look and feel workflow in JUCE has come out of style for all use cases except where it is necessary to change the design language around a lot. For all other purposes it leads to extremely verbose and overly encumbered implementations.
The more modern way would be to use custom components that incorporate the style/design in their implementation. AmbiCreator and StereoCreator already use this approach, so it would be synergetic to use it in PolarDesigner as well.
Additionally, the way LaF is implemented right now breaks a lot of the encapsulation that makes it useful in the first place (layout/placement code in LaF, etc.).
If the plugin is ever refactored to get rid of 3rd party GPLv3 licensed code, this would be a perfect time to tackle retiring the custom LaF as well.