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

List:       kde-usability
Subject:    Re: [PATCH] Kicker applet context menu simplification
From:       "Jamethiel Knorth" <jamethknorth () hotmail ! com>
Date:       2004-04-19 22:20:13
Message-ID: BAY7-F125ym8YhAkZLQ00007bc7 () hotmail ! com
[Download RAW message or body]

>From: Maurizio Colucci <seguso.forever@tin.it>
>Date: Mon, 19 Apr 2004 17:46:14 +0200
>
>On Monday 19 April 2004 13:57, Jamethiel Knorth wrote:
> >
> > The panel is not like a window. The panel is always there but little
> > changes. The panel is rarely resized or moved or rearranged.
>
>Rarely, yes. But *sometimes* you need to add something to the panel or move
>the panel, etc.

Currently, you can edit the panel.

> > Thus, the
> > controls which allow such activities need not be in plain view.
>
>Agreed, not in plain view, but they must be accessible *somehow*.
>And this "somehow" should not be the right mouse button, due to the
>inconsistency.

It is only slightly inconsistent. Applets are part of the panel. If I saw a 
good alternative I would take it, but I still do not.

> > Adding a
> > control button removes a great deal of flexibility from the panel.
>
>I don't see why.

It means I need a certain button. That isn't true right now, and I want it 
to remain not true.

> > In
> > normal operation as the situation is currently, the panel can be 
>customized
> > in any way whatsoever and still be fully useable. You are proposing to
> > remove that functionality for the sake of cleaning up those context 
>menus.
>
>  There must be a mistake. :-) I am not proposing to remove any 
>functionality.
>I am proposing to add something.

You are reducing customizability.

> > The value of flexibility and a better look
>
>A control area would make the panel look worse?

Yes. It would give me something I need to have which I do not want.

> > trumps the value of consistency
> > in this case.
> > I say that with the utmost care, as I value consistency very highly. The
> > inconsistency between the menu items is bad. However, having 
>'consistency'
> > between windows and the panel is bad as well. they are not the same and
> > should not be treated the same.
>
>Does not follow. IMO, two concepts should always be unified if there is no
>reason not to. (for obvious reasons of minimality)
>
>You still have not supplied a reason not to.

It interferes with the customizability of the panel. That has been my reason 
all along. I guess I was not clear on that in earlier messages.

> > Also, possibly you could supply a mockup of what this control area would
> > look like. Mayhaps you have an idea of how to actually integrate this to
> > make it acceptable. I have doubts, although it would be nice.
>
>The panel control area could be something like the blue area in the 
>picture.

Well, seeing that image, it is definitely a bad idea. That doesn't have much 
room for customizability and doesn't fit itself to the theme at all. It 
depends on me having a defineable 'end' to my panel, when it could easily be 
floating in the middle, and it's very much designed for me to have a KMenu, 
which I may not.

_________________________________________________________________
Get rid of annoying pop-up ads with the new MSN Toolbar – FREE! 
http://toolbar.msn.com/go/onm00200414ave/direct/01/

_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic