On Wednesday 07 January 2004 18:17, Aaron Seigo wrote:

> the key is the navigation and feedback interface not the panels, the names
> of the panels, the hierarchy they are in, the order of tabs on the left or
> any other part of kcontrol. those items are all things that can and should
> be addressed only after the main interface has been properly refitted. 

Right, the structuring(naming, hierarchy) depends on navigation and is all 
changed in one bundle. But there is still things which are for sure, 
independent of navigation/Layout:

* There will for most likely be a "Hardware" toplevel(somehow) category for 
example, and this allows some "filing" done.

* The content of the kcm's will not change and their names can be changed to 
better reflect content. Other cosmetic name changes can be done.

* Agree on whether application specific settings should reside in KControl and 
how much administration-ish stuff should be in KControl(or somewhere else).

* Merge similar kcms.

I know navigation is a hard subject so /I/ haven't touched it although others 
have pondered on it. Although, there is perhaps things in my suggestions that 
possibly is made redundant regarding "navigationional" changes(as you say).

But really, the interesting part of that discussion(beware shameless plug, ego 
trip) is the quite different(IMHO) way off adressing KControl's usability 
issues from a organisational perspective. It could certainly need some 
pondering and your opinion. Later(perhaps tonight) I will post some docs 
which makes it a little bit more concrete to judge, although this post says 
most of it:
http://lists.kde.org/?l=kde-usability&m=107342461301033&w=2


			Frans

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