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

List:       kde-devel
Subject:    Re: Where is located the code of oxygen style
From:       "Robert Knight" <robertknight () gmail ! com>
Date:       2009-01-01 19:37:01
Message-ID: 13ed09c00901011137j24b08d49q74289c35b251e466 () mail ! gmail ! com
[Download RAW message or body]

> Therefore, they should obey
> the style for that platform (whatever the style is) and not try to
> override the style decisions with hacks or stylesheets.

The obvious question is "do users think it looks good or not"?  I
think it depends on the expectations the target audience have on each
platform, on Windows of course Microsoft are very much encouraging
users to use non-stock backgrounds and themes for certain
applications - hence Expression Blend - and I get the impression that
the new Yahoo Messenger WPF client is pretty much what they had in
mind.  For 'business' applications maybe not so much.

On Mac, Apple set a look and feel and the expectation appears to be
that others follow it.
On Linux, there isn't such a clear answer, although if consulted the
vocal minority will usually tell you that it should look 'native'
(which usually means the current KDE or Gnome theme).

> For example, the horrid Windows file dialog (or the GTK one)
> should be avoided at all costs.

The Windows Vista and KDE 4.2 file dialogs have the same basic layout,
there are some
differences in the feature set I'm sure but to me they don't seem all
that different.  With regards to GTK,
fair enough.

Regards,
Robert.

2008/12/31 Thiago Macieira <thiago@kde.org>:
> David Johnson wrote:
>>> But why shouldn't he do that, if he likes the style? Unless he
>>> hardcodes the style selection, that is.
>>
>>There are two schools of thought here. One that the application should
>> look like other apps on the platform, and the other is that the
>> application look the same on all platforms. Both are valid.
>
> That's the school of thought I subscribe to. I think applications should
> look and behave the same in a single system. Therefore, they should obey
> the style for that platform (whatever the style is) and not try to
> override the style decisions with hacks or stylesheets.
>
> (Stylesheets are provided for fine-tuning or exceptional circumstances,
> not for the full styling of the UI)
>
> I don't know what KDE on Windows looks like (I don't use Windows), but if
> I were to use it, I'd expect KDE applications to obey the settings I set
> and look like "normal" Windows applications (whatever that may mean, since
> there are tons of different looks on Windows and Microsoft has a lion
> share of the blame; on Mac, the situation is clear). Unfortunately, there
> are too many annoying things that cannot be changed in that OS, so I
> wouldn't try to make KDE out of Windows. Use KDE-Workspace if you want the
> full thing.
>
> However, I draw the line where usability is concerned. Use of native
> styles and widgets and dialogs are good as long as they don't impact on
> usability. For example, the horrid Windows file dialog (or the GTK one)
> should be avoided at all costs.
>
> --
>  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
>    PGP/GPG: 0x6EF45358; fingerprint:
>    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
>
>
>>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
>
>
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]