[Cmb-users] Dealing with passwords in attributes

[John Tourtellott]

I would vote for modifying StringItemDefinition to add either a boolean
flag (IsPassword) or maybe a "type" enumeration with 2 choices (Text,
Password). To me, the closest analog is the html <input> element, which has
a "type" attribute that can be set to *many* different values -- e.g.,
button, checkbox, color, date, file, hidden, radio, url -- as well
as"password" and the default "text". As for the many other "type" choices,
the ones relevant to simulation preprocessing are already handled
differently in SMTK; so I would go for the boolean flag.


On Mon, Feb 1, 2016 at 8:36 AM, David Thompson <david.thompson at kitware.com>
wrote:

> > We have a use case where we need prompt the user for a password in order
> to launch jobs.  ...
> > In order to provide support I can either add a "role" parameter to the
> string item indicating it is a password or create a special item/item def.
> > ...
> > Any comments?
>
> If adding a "role" adjective to items, I would add it to the base Item
> time instead of just to String. It will be handy elsewhere just like in
> HTML5 (where roles are used by browsers to modify touchscreen keyboards
> depending on whether numbers, e-mail, or URLs are being entered[1]).
>
>         David
>
> [1]: http://html5tutorial.info/html5-contact.php
> _______________________________________________
> Cmb-users mailing list
> Cmb-users at computationalmodelbuilder.org
> http://public.kitware.com/mailman/listinfo/cmb-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmb-users/attachments/20160201/635e56bf/attachment.html>