Re: [PATCH datacenter-manager/yew-widget-toolkit 0/2] auto-installer: set proper tooltip for command line show/hide

[Dominik Csapak <d.csapak@proxmox.com>]

On 5/28/26 2:15 PM, Thomas Lamprecht wrote:
> Am 28.05.26 um 13:19 schrieb Dominik Csapak:
>> i get what the end result should be, but i don't think we should
>> override the 'password' feature with something else.
> 
> Why not? A generic "this includes a secret" field seems to be a good
> fit for both? Why duplicate that? (honest question)
> 

Judging from the past, we generally don't have any such fields where
it's not a password, so I don't think we'll use this often.

I think we have to be careful what we add to the public API of
the widgets, otherwise we'll add a ton of stuff we don't (often) use.

E.g. the next one maybe needs a different icon for the peek trigger,
or want it left, etc.

Maybe the answer here could also be that the peek trigger be a custom
one? then it's generic enough for my taste to include it.

E.g. something like (would have to flesh out the details of course)

pub peek_trigger: Option<(Trigger, bool)>

(which could get a sensible default implementation)

this way we could also get rid of the 'show_peek_icon' property
and just set it to None on the use site

Don't get me wrong, we can add this property if you prefer that.

>>
>> another way to do this would be to have a custom trigger
>> on the use site and show '******' manually?
>>
>>
>> i just don't believe we will have many uses for changing this tooltip..
> Sure, but what's the cost of having it vs. duplicating the field for
> just having custom tooltips?