Am 25.11.21 um 20:14 schrieb Vladimir Sitnikov: >> The second variant would hide the expression text in the two static cases. > I thought behind those lines as well. It might be we could add a small > marker that > informs the user that checkbox is configurable. > > ---- > > I just attended a talk by > https://www.smashingmagazine.com/author/vitaly-friedman/ > I asked Vitaly for the ideas for this "crazy checkbox" UI element. > > As expected, Vitaly was quite puzzled, so unfortunately I got no ideas :) > > --- > > One more idea would be having "regular" and "expert" modes, where regular > mode looks like checkbox, > and in expert mode, all "supercheckboxes" always show their "text fields". > > Vitaly said regular/expert modes are a good pattern for UI. > > In other words, "the first variant" by Felix could be "expert mode", and > "the second variant" could be "regular mode".
How would you trigger those modes? Another checkbox? (I sometimes think, we should try to make all those properties we have available in a GUI somewhere) > > --- > > One more option is to show the text field in a popup/tooltip: > [ ] ▼ enable element > > When you click on ▼ (triangle down or whatever), a popup appears that > overlays extra controls for the checkbox in question. > As an extra, it could contain extra information like JMeterProperty name, > option for configuring the field from a command line, etc > > It could be a right triangle, so it "folds/unfolds" the text field (and > "global expert mode" unfolds all the folded fields) Yes, that would make it more clear, that there are more possibilities to use the checkbox. Would the "enable element" text be visible or is it a marker to higlight, that the triangle would be used to enable the element? I think it is important to have the two boolean states plus a third form to be able to convert older checkboxes to such a new ui element without breaking the old save format. Felix > > Vladimir >
OpenPGP_signature
Description: OpenPGP digital signature
