Issue 88127

Summary: The MasterPassword dialog needs new UI.
Product: General Reporter: mikhail.voytenko
Component: codeAssignee: thorsten.martens
Status: CLOSED FIXED QA Contact: issues@framework <issues>
Severity: Trivial    
Priority: P3 CC: frank.loehmann, issues, liujiaxiang, peter.junge,
Version: DEV300m2   
Target Milestone: OOo 3.1   
Hardware: All   
OS: All   
Issue Type: PATCH Latest Confirmation in: ---
Developer Difficulty: ---
Issue Depends on:    
Issue Blocks: 72764    
Description Flags
The patch for the redisigned UI none

Description mikhail.voytenko 2008-04-10 11:30:39 UTC
The current master password dialog has relative poor interface.

mav->fs: Could you please provide a specification for the new UI for master
password dialog. As for the document dialog it would include
- master password creation dialog ( with error message regarding wrong
confirmation password )
- dialog to enter master password for authorisation
- error message about wrong master password
Comment 1 mikhail.voytenko 2008-04-10 11:32:28 UTC
mav->fl: Sorry for the typo, I wanted of course to ask you to design the dialogs. :)
Comment 2 mikhail.voytenko 2008-09-02 10:37:35 UTC
mav->fl: Sending to you as discussed.
Comment 3 mikhail.voytenko 2008-09-02 11:39:03 UTC
Comment 4 mikhail.voytenko 2008-09-10 07:36:59 UTC
Taking the issue back since the design was successfully introduced in
specification ( entry 6.2 ):
Comment 5 2008-09-24 02:24:46 UTC
Created attachment 56787 [details]
The patch for the redisigned UI
Comment 6 mikhail.voytenko 2008-09-24 06:23:44 UTC
Thank you for the patch. I will integrate it in one of the next framework
Comment 7 mikhail.voytenko 2008-11-14 14:00:21 UTC
integrated in fwk92
Comment 8 mikhail.voytenko 2008-11-24 21:31:45 UTC
mav->tm: Please verify the new dialog. The specification can be found using the
following link ( entry 6.2 ):
Comment 9 thorsten.martens 2008-12-08 10:25:59 UTC
Checked and verified in cws fwk92 -> OK
Comment 10 thorsten.ziehm 2010-02-22 14:59:36 UTC
This issue is closed automatically. It should be fixed in a version with is
available for longer than half a year (OOo 3.1). If you think this issue isn't
fixed in the current version (OOo 3.2) please reopen it. But then please pay
attention about the field 'target milestone'.
The closure was approved by the Release Status Meeting at 22nd of February 2010
and it is based on the issue handling guideline for fixed/verified issues  :