Linked by Thom Holwerda on Tue 18th Jan 2011 22:18 UTC, submitted by alinandrei
Ubuntu, Kubuntu, Xubuntu De kogel is door de kerk. After years of focussing entirely on Gtk+ and GNOME, Ubuntu will finally start evaluating Qt applications for inclusion in the defaukt Ubuntu installation. Mark Shuttleworth announced the policy change on his blog today.
Thread beginning with comment 458953
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Talk about arrogance
by Thom_Holwerda on Wed 19th Jan 2011 00:05 UTC in reply to "RE[4]: Talk about arrogance"
Thom_Holwerda
Member since:
2005-06-29

That's a theme engine.

Read the article again. This is about the settings backend. A theme engine ain't gonna help you there.

Reply Parent Score: 2

RE[6]: Talk about arrogance
by lemur2 on Wed 19th Jan 2011 00:16 in reply to "RE[5]: Talk about arrogance"
lemur2 Member since:
2007-02-17

That's a theme engine. Read the article again. This is about the settings backend. A theme engine ain't gonna help you there.


It gets you a long way there (although I agree there must be more to it than just a theme engine). On my system, GTK applications look virtually identical to "native" KDE/Qt applications, in that they all use the same Window styles; widget styles; system, window and application fonts; colours; printer settings; language settings; currency formats; etc, etc. Some GTK applications will even support KDE-style dialog boxes.

Surely such an approach is already far less eclectic than some other desktops, such as Windows for example.

Since it already exists, why not just go with that?

Edited 2011-01-19 00:19 UTC

Reply Parent Score: 4

RE[6]: Talk about arrogance
by segedunum on Wed 19th Jan 2011 14:29 in reply to "RE[5]: Talk about arrogance"
segedunum Member since:
2005-07-06

That's a theme engine.

Yer, and? It's certainly a big help to desktop and application integration - and guess who wrote it? We'll just paint over that though.......

Read the article again. This is about the settings backend. A theme engine ain't gonna help you there.

This is about integrating applications, not purely about some settings backend. A settings backend by itself certainly won't help you because you've got to agree a format with everyone as to what settings will be stored and how they will be used, and everyone has to buy into it for it to work. The article goes into no detail whatsoever there.

Stop telling people to read the article again when you don't understand the implications within it yourself and Mark Shuttleworth doesn't either.

Reply Parent Score: 3