This PR first moves selectItem() to the end of the callbacks struct, presuming that UI callbacks will be added/modified more than others. Then an enterText() callback is added along with related struct and flag types.
The purpose of the enterText() callback is to allow users to enter credentials such as a password for an encrypted certificate chain and private key, or username/password for a credential server. Other uses are possible, too.
The big question is: are we just going to end up adding a number of UI-element specific callbacks, and it would be better to start out with a more general and extensible forms interface? I'll work on a proposal for such an interface in a separate PR (probably not before the new year, though).
This PR first moves
selectItem()
to the end of the callbacks struct, presuming that UI callbacks will be added/modified more than others. Then anenterText()
callback is added along with related struct and flag types.The purpose of the
enterText()
callback is to allow users to enter credentials such as a password for an encrypted certificate chain and private key, or username/password for a credential server. Other uses are possible, too.The big question is: are we just going to end up adding a number of UI-element specific callbacks, and it would be better to start out with a more general and extensible forms interface? I'll work on a proposal for such an interface in a separate PR (probably not before the new year, though).