Slashdot Mirror

← Back to Stories (view on slashdot.org)

GTK-Themes To Be Supported By KDE2

Posted by Hemos on from the here's-something-for-your-eye-dekker dept.

Tackat wrote to us regarding the recent announcement from the KDE folks concering KDE2. While KDE has had widget themes and such, the people behind KDE have announced support for GTK Themes. For some screenshots, check out the announcement body.

6 of 117 comments (clear)

  1. Re:GTK-Themes To Be Supported By KDE2? by nitehorse · · Score: 4

    Qt only provides very bare technical support for the GTK themes - the only support that it provides is that it can load pixmapped widgets. KDE actually implements the GTK themes and displays them with Qt- so the article is not mistitled.

    Hope that was informative.

    -Chris

  2. One more step away from the "forking" argument by Kissing+Crimson · · Score: 4
    For a few years now, Linux opponents have been doling out dire warnings about forking issues. It has been said that eventually there will be too many choices and not enough interoperability.

    Too many choices? Ludicrous concept.

    Once again, we see different software organizations working toward the same goals; lots of choices with few drawbacks to any one option. Even software groups in competition are now working toward interoperability.

    Coincidence is the Superstition of Science

    --
    What's that smell? Ah, that's my karma burning...
  3. Hey guys, *read* the announcement by vanza · · Score: 5

    Lots and lots of people have been saying "cool, GTK themes!" and such. Note that, as some have already pointed out, KDE will support GTK *Pixmap* Themes.

    This means that those nifty GTK Engines won't work, because they rely on how the GTK library implements themeing, and it is most surely different from the way KDE and Qt implement themeing.

    Another misleading link from the article is the kde.themes.org link. kde.t.o only carries KDE 1.x themes, and KDE 1.x has *no* mechanism for widget themeing, aside from window decorations using pixmaps.

    This thing that KDE is doing can probably also be done for GTK: build and engine to understand the KDE 2 pixmap themes (I read somewhere that there is an engine for pixmaps themes on KDE 2 ... maybe a look at http://www.mosfet.org/themeapi/ would help.)

    As for perfomance, I can't say much because I'm not a developer for any of them, but the KDE team has been talking much about this "really cool pixmap cache" that is supposed to be really fast...


    --
    Marcelo Vanzin
    --
    Marcelo Vanzin
  4. Re:Nice, but why not just use GTK? by stripes · · Score: 4
    Qt is native C++

    Last I checked Qt was actually a slightly extended C++, there was a pre-processor that would turn event/slot things into real C++ code.

    For those of us who want a good C++ toolkit, this is much better than some terrible C++ wrapper of a C toolkit (and faster as well).

    On the other hand I remain utterly unconvinced that Qt is better then a good C++ wrapper of a C toolkit. And I am totally convinced that Gtk-- is not just a good wrapper, but a great one.

    Sigc++ (the slot/event scheme Gtk-- uses) also handles events faster then Qt's event system according to a biased benchmark. I don't know how fast or slow the rest of the system is as opposed to Qt. It seems quite fast enough on a slow (PPro 150) machine, so I'm content to leave well enough alone.

    Personally I don't like C programming and much prefer C++/Java.

    Perfectly reasonable. I like C++ with the STL more then I ever liked C, and Java was a pretty nice language for the few things I have done with it.

    Thus I use Qt. If you want to use C, use GTK+.

    This doesn't follow. I really urge you to check out Gtk--, if for nothing other then to see how much nicer the slot/event model is implmented.

    There may be other reasons to use Qt. There may be other reasons why KDE might be better then GNOME. But this just isn't a valid reason.

    Down on the farm, we call that having a choice and that is a good thing.

    Indeed it is.

  5. Re:Why stop at GTK themes? by Outlyer · · Score: 4

    Well, it's not quite that simple. QT and GTK both use different mechanisms for communication between windows. Not the least of which is the fact that GTK is a C library, while QT is C++. Yes, I know that there is a C++ wrapper for GTK, but the interfaces are really different.

    While your somewhat anecdotal assertion that QT is inferior may be true in some regards, many programmers prefer it's models, while others (like me) prefer GTK. To move everything to one toolkit denies freedom of choice, even if it might make things easier. Just use a GTK theme in KDE so you can have the look, and you don't have to force people to use the same toolkit.

    --
    ----------------- "I have a bone to pick, and a few to break." - Refused -------------------
  6. Re:That's quite a shot. by boloni · · Score: 5

    Pixmap themes are essentially images painted over the controls. Widget themes on the other hand, are actual code, loaded dynamically which draws the controls. This make it not only faster, but allows to change the way in which the control behaves. For example, in some styles KDE scrollbars have 3 buttons (2 down + 1 up), combining the advantages of different toolbar styles. With a pixmap style you can change how the button looks, but you can not switch between different behaviors. Lotzi