[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: fonts control center module improvement
From:       Luciano <mikelima () virgilio ! it>
Date:       2003-05-24 19:45:01
[Download RAW message or body]

On Saturday 24 May 2003 21:11, you wrote:
> On Sat, May 24, 2003 at 08:33:35PM +0200, Luciano wrote:
> > So far, I played with the UI, I am going to implement the real stuff
> > soon. A snapshot of what the dialog will look like is at
> >
> > http://www.kde-look.org/content/show.php?content=6281
>
> Does "Remove Scheme..." really bring up another dialog ? Why ?
> If it doesn't, the ellipsis is wrong.

Actually not, it is a cut&paste error. I am using the "colors" panel
as a reference, since I think having the same interface would reinforce
predictability of the two panels.
 
>
> There is no visual association with the scheme selector and the actual
> items contained within the scheme (which I assume are the fonts above.
> For example, there's no way to work out if the anti-aliasing settings
> are in the scheme or not (I guess not, but the user should not have to
> guess, they shoould be given visual hints).
>

I'd say that antialias setting should be set independently, however, seeing 
that in the control center the contrast setting is packed with the colors,
I think I should save the antialias setting with the scheme.


> What is the use case for "Import Scheme" ? Will drag and drop work ?

Import scheme should open a file requester, and add a pre-packaged scheme
to the list and the user configuration directory. I have not thought about 
drag and drop yet. 
 
>
> Why does Save Scheme exist at all ? You already have a "Cancel" button.
> The scheme should be saved on clicking OK, and changes abandoned on
> Cancel.
>

Save Scheme is needed to add a new scheme to the preset list. 
The user selects her preferred fonts and then clicks on "Save Scheme...".
A pop up asks for a name, and the scheme is added to the list.
The Font requesters above assume the role of a preview of the fonts.

> How does a user create a *new* scheme ?
>
> I'm not sure the repetition of "Scheme" in the scheme group box is a
> good idea. The visual context should disambiguate...

"Save" is already used by the panel...
If you have some better idea for the labels, I am open to suggestions.

>
> One possibility would be :
>  |--Font Scheme------------------------------------------------------
>  |  -----------------
>  |
>  |  | My Scheme  |\/|
>  |
>  |  -----------------
>  |
>  |  General: | .....  |
>
>  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
>
>  |                                                |New| |Import... | |
>
>  ---------------------------------------------------------------------
>
>  |--Anti-aliasing-----------------------------------------------------
>  | [x] Use anti-aliasing for fonts + rest
>
>  ---------------------------------------------------------------------
>
>  | Help | ...
>

I am sorry, but I am not sure I understand your ascii art. 
Do you prefer the Scheme selector to be grouped with the font requesters,
is that it?

> regards
> john
>
> p.s. what does the mnemonic for An_t_i-Aliasing actually do ? It seems
> a bit odd for a group box.

Uh, I don't know, but that is not my doing. It's been there all the time.

Best regards,
Luciano
_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]