Matthias Clasen wrote:
> On Sun, Mar 1, 2009 at 7:47 AM, Sven Neumann wrote:
>> So perhaps as a start, try to make a list of the features that are
>> needed, or might be useful, in a password entry?
>
> Some of the recently added new features are specifically for password
> entries, like the caps
Hi,
On Sun, 2009-03-01 at 14:47 -0500, Matthias Clasen wrote:
> Some of the recently added new features are specifically for password
> entries, like the caps lock
> warning.
Great, so if we had a GtkPasswordEntry, these features would not have to
live in GtkEntry. That's even better.
> A pass
On Sun, Mar 1, 2009 at 7:47 AM, Sven Neumann wrote:
> Hi,
>
> On Sun, 2009-03-01 at 01:01 +, Stef wrote:
>
>> This leads me to wonder if perhaps the password entry control in GTK+
>> might fare better as a separate widget. There's an insane amount of "if
>> (entry->visible)" in the code and al
Hi,
On Sun, 2009-03-01 at 01:01 +, Stef wrote:
> This leads me to wonder if perhaps the password entry control in GTK+
> might fare better as a separate widget. There's an insane amount of "if
> (entry->visible)" in the code and alternate code paths for password entry.
I definitely think so.
A while back Matthias asked on the gnome-keyring mailing list why we
were shipping our own forked GtkEntry. [1]
I explained that one of the goals of gnome-keyring is to try and keep
passwords and encryption keys out of the swap file by storing them in
non-pageable memory. The forked GtkEntry initi
