Feature Request: Common and contextual vanacular for controlls

[Crypter0]

The current controls are oriented toward the engineers who built them because they represent how the software functions.

This seems natural to an engineer who is building it or a user who has read the manual, but it is difficult for an end user to utilize.

Since you have thousands more customers than engineers who write your code it would be more efficient for our community if you either labeled things for end users or had different UI control labeling schemes based on the type of user.

As an example, based on the behaviors of the software rather than it's implementation the following controls should be named something different if you want someone to just be able to jump in and use them. I have experience with user interface design, software development, and quality assurance, and I think the following examples give a general direction of what I am trying to describe.

Here are a few examples:
Sampling Steps : A slider with the label Effort (how long the system spend trying to come up with an idea of what to make.)
CFG Scale : Enforcement (how much I want it to give me exactly what I asked for)
Denoising Strength : A slider with Creative on one side and Stability on the other (how much I want to sacrifice diversity to get a stable image)
Upscale By : A slider with Unrefined at one end and the Target Resolution value at the other. This is because upping the resolution decreases the raw nature of the image and the ability of the user to create images that are generally considered less palatable.

In the above examples I have applied new mind to determine what the controls should be named based on the the behaviors of the software when a control is changed in common words that relate to what a novice user is thinking about when trying to create an image rather than building the software.

If you are looking for someone to work on these things please let me know, god knows I can use the work.

[email protected]