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

List:       kde-devel
Subject:    Re: Bug#4297: What does the buttons on the left side of kscd Represents?
From:       Michael Reiher <michael.reiher () gmx ! de>
Date:       2000-06-05 14:37:43
[Download RAW message or body]

Waldo Bastian wrote:
> 
> Just for the record:
> 
> An application really doesn't need to have a menubar to be KDE compliant if
> it has a good reason for not having a menubar. However, _IF_ an application
> has a menubar it should act like the menubar described in the style guide.
Sure, but IMHO itīs better to have one. As itīs easier to use for unexperienced
users. As it is a scheme that all DEīs use and thus people are used to it. But
I already said that.

> 
> kscd is a good example of an application that doesn't need a menubar because
> its interface is set up to resemble a real-world CD-player.. and real-world
> CD-players don't have menubars.
Sure, but they also (normally) donīt have lotīs of cryptic symbols.

> 
> The price you pay for not having a menubar, as application developer, is that
> you need to think really hard to come up with a good solution for things like
> configuring since real-world CD-players don't have "configure-buttons"
> neither.
Right.

> 
> "knotes", another application without menubar, solves this problem by making
> all functions available through a RMB menu. I think this could be  a good
> solution for kscd as well.
But itīs harder to use then a menu bar. We probably have our reasons why KDE
applications donīt have Gimp like menus. Further, do we have key combination to
open context menus? Menubars are accessible by keyboard.

Greets

Michael

-- 
Michael Reiher                                    :  michael.reiher@gmx.de
Student of Computer Science at TU Dresden/Germany : mr23@inf.tu-dresden.de
KDE Developer                                     :         reiher@kde.org

"Beware the woods at night, beware the lunar light!"
 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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