I like the current module selector, being in two dimensions/table format means it quicker to get to specfic modules faster - esp. as the number of plugins grows.
I do agree with the the abbreviations being cryptic
though honestly, using the SSP regularly means I know at a glance what they all are, so not that tricky - however, as plugin list grows I can see that getting harder
perhaps a compromise would be to have a one line ‘status bar’ at the bottom of the browser - this could display an expanded name/description (VSTs have a description field that could be used)
therefore as you move around, you would see this at the bottom of the window.
abbreviations on encoders/buttons I think (personally) is more confusing…
however, Im not really sure I have a solution…
I’ve first hand experience of building UIs for the SSP, and the issue I had was for context, you need the label to be above the encoder and in a context layout for buttons, doing this at a reasonable font size, and you soon find your limited to very few characters.
then add to this the idea of two values per encoder (something on a few modules)
this is useful on modules, since a user can see it without having to switch pages.
BUT it again reduces the label size.
so its a challenge on the SSP because we do not want tiny fonts either.
I used to have help pages on the module (I still do on SWAT) , but ran out of buttons which made it awkward, also I didn’t really find I had enough space to be useful… (and its load of dev effort to do it).
though I wonder if perhaps like the browser, a full name could be display when the encoder is turned?
on my modules often parameters ‘pop up’ when you turn the encoder - so I could display a ‘full name’ at that point - however, that wont work in all situations.