[kde-guidelines] Some comments to KDE-HIG content

[Frans Englich]

On Thursday 09 September 2004 12:48, Siegfried Olschner wrote:
<SNIP>
> 6)  General content - Level of detail
> I do not agree to your statement that defined pixel spaces between
> dialogelements are not necessary. E.g. the configuration dialogs of kword
> show
> - Different spaces between frame of a box and next dialog element
> - Different widths for spinboxes (different look, too)
> - Different spaces between text label and following combo box
> - Different spaces between frame of tab filed and frame of box
> - Different use of location for text label for slider
> http://www.suse.de/~sigi/projects/kde_hig/koffice_01.png
> If qt is used by one developer with default settings, he will get a unique
> look & feel, but qt with x developers will produce differences.
>
> Also the different width for some KDE configuration dialogs could be an
> example. See the dialogs of Konqueror, Kmail, Korganizer at
> http://www.suse.de/~sigi/projects/kde_hig/selection_list_box.png
>
> I know the power of selfadjusting width for different languages, but I
> think it is necessary to define the default layoutSpacing and layoutMargin,
> the general use of the stretchable dialog elements with stretchable
> spacers. A strong micro usability via well defined spacing will result in a
> strong consistency and a strong professional look & feel. Perhaps the user
> cannot name the inconsistency directly, but in his subconscious he will see
> it - and perhaps think "oh, Apple applications look very very professional,
> ... and this not" ;-)
<SNIP>

We of course want a widget layout which is consistent down to the pixel, but I 
don't think that's best /achieved/ by specifying it in the HIG. Because Qt's 
geometry system is not(from the API user's perspective) "absolute position" 
but functions on a higher level. The cause to the inconsistency you describe, 
is people don't use the API properly. The solution is to make sure people use 
the API properly, and then make the widget themes set the values right:

1. The HIG promotes and explains how to use 
KDialog::spacingHint()/marginHint()
2. The CIG deals with how to select widget theme, and how to design one

Then we make sure people follow the HIG(the hard part), and adjust the widget 
themes so the valus are right.

I also see this as preferred because the actual layout is then not 
decentralized and yet another thing the developer can mess up, but 
centralized in the widget theme.


Cheers,

		Frans