According to some posts the projucer gui is deprecated?
The GUI editor is more or less deprecated and won’t be developed any further (afaik). You will have way more freedom and possibilities of placing your components when you do it by hand (by code, quite similar as the plug-in tutorials show you).
On a related note, I have seen a couple different WYSIWYG editors for Juce, do they have particular strengths and weaknesses?
PluginGuiMagic :
I completely get the value of designing in a live environment. That’s why I created PluginGuiMagic (dual license) in the meantime. It is a 3rd party module that adds the missing features:
more signal visualisations (level meter, analyser, frequency response plot for IIR, can be extended)
more LookAndFeels (to be continued)
FlexBox layout
CSS-like property inheritance
editable without coding while the GUI is running
extendable with your own components
usable in JUCE plugins as well as applicati…
JIVE :
JIVE is a bundle of JUCE modules centred around the desire to have a more modern approach to building GUIs in JUCE. As well as some handy utility modules, JIVE has two main constituents:
Melatonin :
Here’s a JUCE module I’m working on, based off of Figma’s UI and @jimc ’s Component Debugger from his juce-toys :
Pop the module into your project to visually inspect the UI you are building “in place” as well as visualize the component hierarchy. You can resize components in place, which lets you nudge things around while designing to get accurate numbers without needing to add JUCE_LIVE_CONSTANT everywhere. I plan to expose property display/editing for things like font size, colors…
[image…
Just from reading those blurbs I would guess: PluginGuiMagic for audio and filter visualizations, JIVE for apps with a modern web feel, and Melatonin if you are a stickler for writing code (it only inspects, not saves, layouts).
I have no experience with any, I will probably try out Melatonin first.
1 Like
