* change "Lock as private" to just "Private". the phrase "Lock as
private" is
a bit awkward (it is not a natural phrasing one would use in
conversation) and
specifying "Lock" speaks to the mechanism rather than the intention
of the
user. the intention is "this is private"; the mechanism we use is
"locking
it".
Before integrating this phrase we tested with a lot of people. We tested
different words and phrases like "protect, lock, mark...as private,
secure" etc.
The result has beenthat most people preferred and understood the
phrase "lock as
private". Here both results, the locking of the activity with a
password AND the
encryption of the private data, have been understood.
Only "Private" would not clearly communicate the underlying action
for the user.
I don't really like "Lock as private", but if that's the one that
fared best with the users, I think we should still keep it. Don't know
what it looks like if it's placed next to the name, though. Might make
the row a bit too long.
Keep in mind that we have an error message quoting "this is a dulicate
name" or something like that in case the activity name is already
chosen. This error message appears right next to the text field.
_______________________________________________
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active
