Unifying GTK & QT Theme Engines

An anonymous reader writes "Some guy on kde-look recently released code that makes gtk apps use the current qt theme. Seems this would be a major development for unifying the 2 environments. From the URL: This GTK theme engine uses the currently selected QT style to do it's drawing. Basically, it makes your GTK apps look like QT ones. "

Comments

Unification in the *nix world

[W32.Klez.A]

While this may seem like a minor thing to some people, every bit of interoperability and unification helps. Naysay as much as you want regarding Microsoft, but the reason why they have the market share is because of the unification present (at least in appearance ;-). If OSS projects (and non-OSS friends of them) can't come together, they should at least work together.

Re:Unification in the *nix world

[Christopher Whitt]

What interoperability ?

I think you mistook the OP comment on interoperability between apps written for different window managers to mean cross-platform portability.

The OP didn't claim windows was interoperable in a cross-platform sense. They were pointing out that on Windows, all apps have the same look and feel.

To achieve that result on Linux, across several common UI toolkits and window managers requires interoperability between apps written for the various toolkits.

Re:Unification in the *nix world

[Xabraxas]

Naysay as much as you want regarding Microsoft, but the reason why they have the market share is because of the unification present

Nope. That is not even close to the reason why they have the marketshare that they have. First of all Mac has a very good unified theme but they have next to nothing in marketshare. If that's not enough to blow a hole in your argument then my next statement will. Third party apps for Windows often use themes that are not anywhere close to the Windows theme. Take Winamp for example.

Windows has their marketshare because of apps, vendor lock in, propietary formats, and a whole bunch of other things that have nothing to do with a unified look and feel.

With that said, I do think this is a step in the right direction. Hopefully one day KDE and Gnome will have unified libraries and a unified interface. I only hope for this so the community doesn't lose one desktop completely in favor of another.

Re:Unification in the *nix world

[B'Trey]

You seem to be under the impression that choice is always a good thing. It isn't.

It doesn't really matter which side of the road you drive on. But it damned well would matter if it changed every time you crossed from one city to another.

The fact is that most users don't WANT to choose which windows manager they use. They want to be able to sit down at a machine and have it look and act in the same way they're used to it acting, whether it's their home machine, the machine on their desktop at work or the one at the corner Internet cafe. For power users and geeks, all this choice is a wonderful thing. For average users, it's a pain in the ass.

If we want Linux to move to the desktop (and that's a genuine "if" - it certainly isn't a given that that's necessarily the best future for Linux) but IF we want to move Linux to the desktop, it needs to be standardized. You can leave all the choices there, just as there's actually quite a bit of customization you can do to Windows if you get under the hood, but there needs to be a standard Linux "look and feel" that is a uniform default across distributions.

Re:Unification in the *nix world

[gujo-odori]

It's even simpler than that. MS has their market share because IBM gave it to them by choosing them as the OS vendor for the IBM PC. All of the lock-in via proprietary formats and engineered lack of interoperability and highly predatory and monopolistic practices came after that. If IBM had chosen CPM as their OS or had written one from scratch, MS today would still be just an application vendor among many. A large one, probably, but still just an application vendor.

Widget Mania

[Speare]

This is a good first step. But it's a tiny baby step.

When I can choose a widget theme once, using a central theme selector, such as GNOME's, and it shows up in all versions of Qt, GTK, Gtk2, Tk, Mozilla, and other applications, then I'll take notice.

The proliferation of toolkits does such a disservice to the desktop, even moreso than the proliferation of desktop environments. Why are there so many?

It seems like most OSS developers must go through the same milestones of skill development: a new C++ string class, a new IRC client, a new window manager, a new toolkit, and a new update package manager. Stop rewriting the wheel and improve what's out there in meaningful new ways.

Re:Widget Mania

[Trick]

Call me crazy, but I'm glad we've got a choice of desktop environments. Not to knock the KDE folks, but I happen to prefer GNOME. If desktops were to somehow "unify," and that meant all we had left was KDE, I'd be more than a bit peeved. I'm sure there are plenty of other people who'd feel the same if GNOME were to disappear so that KDE could be the one true desktop environment.

If that means that some apps won't be completely integrated with my dekstop, I'm fine with that. I'd rather have the choices I have now than be forced to use a desktop environment I don't like.

Re:Just a style

[Shisha]

No one is really talking about unifying the API. That's the bit that developers are most mentally attached to. As we all know GTK vs. QT is rather different in the style of writing code, different mindset even, so it wouldn't work for either side to unify the API. With unified API we'll have loads of unhappy QT _and_ GTK developers!

OTOH this (unifying themes, i.e. one theme working for both QT & GTK) is the first step in the right direction, of making the two indistiunguishable to the user. Next would be _perfect_ cut & paste, including HTML pages, pictures, vector graphics etc. AFAIK freedesktop.org has come a long way working on cut & paste (drag & drop) and apparently all it needs now is more polish.

Final stage would be using kparts in GTK apps and bonobo components in KDE. There are cautious steps in that direction. And then there is OpenOffice (check out cukoo) of course and Mozilla and GNUStep... long way to go till everything is perfect. Then it will be the job of distributors like Mandrake & Xandros to give us the perfect desktop linux. Or our job, for those who like to tweak and fiddle with things. I'm looking forward to all this! (and I hope I'll be seeing less and less GNOME (KDE) sucks!!! style flamewars everywhere. Hey, I don't care whether I'm using Rhythmbox (where the file open dialog is still a joke) or Juk (which uses arts for the sound backend and arts sucks _and_ is a joke), I'll settle for either of the two as soon as it'll be perfect :-))!

Partly a win, partly a problem

[eschasi]

Stating prejudices up-front: I'm a KDE kind of guy.

There's plusses and minuses to this. On one hand, unified theming is a win, no question. But doing so by adding yet another layer of interface could perpetuate the core differences rather than helping unify them. The world is rife with short-term hacks that are still running; it's one of the big contributors to bloatware.

In addition, it's a one-way change. When the author completes his work, Gnome apps can follow KDE themes, but not vice-versa. That's good for KDE, but not particularly good for Gnome.

It also leads to some subtle UI traps. When I run a Gnome app under KDE, it stands out. In one sense that's bad, as it can be visually jarring. In another sense that's good, as I'm visually alerted to expect some different UI rules. If one can't determine which ruleset to follow by a casual glance at the app, it's going to lead to user confusion.

It's also going to dilute the UI guidelines to both KDE and Gnome. Application writers tend to model their UIs on other apps, not from reading the UI guidelines. An app developer running Gnome apps under KDE look (but not feel!) will assume that either the KDE rules are loose or that he should be developing Gnomish features.

I'm not saying the author shouldn't do this; it's a noble goal and (from the responses on the author's posting) pretty decent code for an alpha/beta release. But we should hope for and work towards better long-term theme engines.

Why do we still fight GNOME x KDE

[Anonymous Coward]

I really don't understand most Slashdot readers. In every news about KDE or Gnome people start fighting on what is better, Qt or Gtk, C or C++, Gnome or KDE, with theory on how SuSE buyout will end KDE, why Qt isn't free, that Linus uses KDE, Trolltech is owned by SCO, etc. People who keeps posting things like this must be new to free software, or just don't understand it at all. The goal is *NOT* to kill Microsoft Windows and every OS and have just GNU/Linux with one desktop installed on all computers. The goal is freedom, is choice. I don't want to be like 10 years ago, when I thought DOS/Windows were the only operationg system available. Also, most free software projects are coded for fun. I can assure you, even if the whole world start using Gnome and KDE is just used by it's own developers, KDE will keep existing! There's no desktop war, so there is not going to be a winner. So, understand the community, and stop flames. We should be discussing how great it is that someone is trying to make GTK apps integrate better to the KDE environment, and hoping a GTK coder will start doing the same. I use KDE and I get really happy when I see a new feature on Gnome, cause probably KDE will have it too soon, Gnome users should feel the same way when KDE gets a new feature. And, while we're still talking about this, please, when a project is posted here, let's not comment on how there was already a project with the same goal and how duplicate effort is lame: if someone think it'll be fun to code another mp3 player, let him do it, *For coders, projects are mostly about fun!*