[Bug 299039] New: Make New Activity Password and Activity Password dialogs for private Activities comply with HIG

Thomas Pfeiffer colomar at autistici.org
Sun Apr 29 15:40:13 UTC 2012


https://bugs.kde.org/show_bug.cgi?id=299039

            Bug ID: 299039
          Severity: normal
           Version: unspecified
          Priority: NOR
                CC: active at kde.org
          Assignee: notmart at gmail.com
           Summary: Make New Activity Password and Activity Password
                    dialogs for private Activities comply with HIG
    Classification: Unclassified
                OS: Linux
          Reporter: colomar at autistici.org
          Hardware: Other
            Status: UNCONFIRMED
         Component: Contour activity screen
           Product: Active

The New Activity Password and Activity Password dialogs currently do not comply
with the corresponding HIG
(http://community.kde.org/Plasma/Active/Development/ActiveHIG/Dialogs) in
several ways and thus should be changed:

1. The buttons (OK/Cancel and Unlock/Dismiss) are still placed at the bottom of
the dialog. They have to be moved to the dialog title (as in the Activity
Configuration dialog)

2. The button labels do not comply with the HIG and are inconsistent. To make
them compliant,
 a) The "Dismiss" button in the Activity Password dialog has to be renamed to
"Cancel"
 b) The "OK" button in the "New Activity Password" dialog has to be renamed to
"Save"

3. The dialog titles do not describe actions. They should be changed to:
 a) "Unlock Activity" instead of "Activity Password"
 b) "Set Activity Password" instead of "New Activity Password"

With these changes, the dialogs would be HIG compliant, more consistent with
other dialogs and with user expectations.

Reproducible: Always

Steps to Reproduce:
1. Set an Activity to private
2. Tap "Save and Enter Password"

or

1. Open a private Activity
Actual Results:  
Dialogs inconsistent with HIG and other dialogs appear

Expected Results:  
Consitent dialogs appear

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Active mailing list