I was wondering - are there any plans to improve the inspector UI?
While it’s clear what everything does, the number of buttons and information presented makes everyone’s eyes glaze over when opening the foldout for a localized string or other.
Also, the chance for human error is massive (and thus also cognitive load). During our normal use, 80% of the inspector interface is not only not needed but will break something when used. For example, there is practically never a need to add a Locale from the inspector of a specific string.
As a developer, I’d really like to put some nails into most of the options, to hide them, lock them, or otherwise keep others from breaking everything.
My suggestion would be to add one or more attributes that can be added to a LocalizedString (or other localized class) to hide each option (optionally) and to give it a fixed value (optionally).
For example, while showing the English localization is useful during development, all the other languages are actually not (at least for us, since those will come from a spreadsheet).
Or the table collection - I want to force it to be a specific one, so whoever sets up the string does not have to think about which collection it goes into. It should still show, and be openable with the small button, but not be changeable.
When not using variables, I’d rather hide the list of variables. None of the non-developers knows what to do with them anyway.
I’m aware I can set up an initial collection and key via the field, but this doesn’t keep anyone from selecting something else.
Maybe this could also be solved with a custom drawer. But that’s not for the faint of heart.