Aaron Seigo wrote:

>On February 11, 2004 11:53, William Leese wrote:
>  
>
>>Aaron Seigo wrote:
>>    
>>
>>>>- the menu section should have its own module as the KMenu is not only
>>>>related to kicker but can be shown when clicking on desktop or pressing
>>>>alt+F1, too.
>>>>        
>>>>
>>>this is a technicality. people tend to perceive the menu as part of the
>>>panel.
>>>      
>>>
Infact a good design is one by seeing which a user can easily figure out 
conceptual model(that is what exactly happens at backend). If KMenu is 
part of Panel then people will believe that KMenu is a part of panel(as 
in windows).

Adding a lot of modules in KCM is also not a good idea. May be we can 
have something like related modules, that is when you open Panel 
configuration tab it shows you taskbar and KMenu in list of related 
configuration modules. This idea can be used at other places also, like 
if I am changing my window style it is very likely that I change my 
colour scheme and window decoration.

>>In the current situation things are slightly confusing when configuring
>>a second panel that does not contain the kmenu button, because the menu
>>tab is always present.
>>    
>>
>
>are you truly confused, or just imagining somewhat _could_ be confused?
>do you notice that the panels are listed on the tabs, not globally?
>
>- -- 
>Aaron J. Seigo
>while (!horse()); cart();
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
>
>iD8DBQFAKoKD1rcusafx20MRAhVkAKCByUaj9qXuFyncS7faHQrdYJbD2gCeN8+p
>Kba/Rul9kE2BypUsTfly8MQ=
>=KnHD
>-----END PGP SIGNATURE-----
>_______________________________________________
>kde-usability mailing list
>kde-usability@kde.org
>https://mail.kde.org/mailman/listinfo/kde-usability
>  
>


-- 
Nilesh Bansal
http://www.cse.iitb.ac.in/nilesh/

_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability