Tabs for controls

[ghost]

No description provided.

[baconpaul]

In addition to this, I wanted to ask some questions about the use of JUCE to quickly understand how/what.

• what UI framework did the original Surge use before it was ported to JUCE?

vstgui

• what where the reasons it was ported?

because of many bugs and shortcomings in vstgui

• is the current UI made by a UI designer that can drag and drop widgets to visually build it with minimal code required?

no

• are the current widgets standard JUCE widgets or are there custom widgets too?

custom

• what other UI frameworks were considered when looking for a good choice when JUCE was chosen and why was JUCE the best choice?

myriad reasons why juce was the best choice, including widespread use in the audio field, completeness, portability, accessibility, open source compatibility, and a strong team

[mkruselj]

Adding more tabs is directly against the design philosophy that Claes Johansson initially set up with Surge. Surge is all about minimizing the amount of tabbing the user has to do! Thousands upon thousands of actual uses praise this workflow because it is really superfast when you get to know it. And we do intend to keep it that way. As mentioned before, we will have a player mode for beginners, #6225, but we won't slow down the main edit interface by introducing many more tabs, that would make it a completely different synth, that wouldn't be Surge anymore. And there are many other plugins that cater to those types of users, anyways.

Also, after Surge XT 2.0. which will have a heavily redesigned GUI, with some new features replacing and improving upon some old features, eventually we will reach a feature freeze point when we won't be adding any new stuff in. We have a number of other projects to cater to, as well.

[mkruselj]

then of course it can be a strong idea too: you have direct access to everything.

That is exactly what Surge is all about!