GUI decisions...

[nathanjhood]

Chore

Describe the chore

I'm strictly not a visual/graphical designer. Unfortunately I have absolutely no natural talent for visual design, not even basic 101 stuff like using the right text colour against a given background.

One can only set out to achieve so many things in one's lifetime. I have no aspirations to improve my visual design.

The GUI side of an audio plaugin seems to be even more work than the audio side itself. I'm not really up for that kind of time-sink on something as auxiliary as graphics.

For 1.2.0, I've reverted to the juce GenericAudioProcessorEditor.

I may have a go at overriding this class, or ideally just tweaking the look and feel, on a framework-level basis (i.e., applicable to all my audio plugin work, poentially under StoneyDSP::stoneydsp_graphics).

I'm quite happy with the generic editor for solving the issue for me. It does however mean that the undo manager (and potential preset manager) are not connected to the actual audio processor and thus not implemented in the final build, this way. But for a one-band EQ for analysis purposes, that shouldn't hurt anybody.

(Honestly, this DSP is not what I personally would use for any real-life audio mixdown...)
s
One small issue is that the images in the documentation do not match the current release build visually. Those images are also very quick screengrabs that were done before I realized anybody would ever take a passing interest in this project.

If we stick with the generic editor; the images should be re-done, partially to include the revised GUI.

If we re-implement the old GUI: the images should probably be re-done anyway, cropped to fit sizes that are sane for web browser contexts.

This may be a long-standing chore to file future GUI work under.