If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Agreed that Qt4 emulates Gtk+ about as well as any other *nix toolkit emulates any other *nix toolkit. Qt4 has the dialogues but it fails the moment the Gtk+ environment uses more than one font, it misses settings relating to the display of icons in menus, the display of icons on buttons, the display/placement of scrollbar steppers, ignores a lot of the more complex window matching in the Gtk+ style. Plus Qt4 has a lot of widgets for which Gtk+ has no analogue, like dial widgets, the markers on scale widgets (although they're coming) and plasmids, which look really out of place in a Gtk+ environment.

hey I know how it should look, but it broke after some time, some updates etc, and it stops look ok, was also experimenting with theme and other stuff.
So.. icons was ok
but text in input box is same color as background anyway, need to change motive for that.

i use GTK i dont say its better or worse i just like it
QT is also good, but i HATE HATE HATE HATE when you use arguments, that QT is KEWL because it looks good on GTK and GTK on Qt doesn't.. its bullshit

i use GTK i dont say its better or worse i just like it
QT is also good, but i HATE HATE HATE HATE when you use arguments, that QT is KEWL because it looks good on GTK and GTK on Qt doesn't.. its bullshit

both libraries are good, I prefer GTK

There you go. That's the right answer, folks.

The truth of the matter is that there's pluses and minuses with each of the popular (key word there...) toolkits and the argument that was getting used is a bit bogus. More to the point, arguments of "native look and feel" keep getting pushed around and while it's a nice sentiment, that "native look and feel" isn't so much so or is obtained by using the Vendor's own toolchain to DO it.

There have been attempts over the years to accomplish this task within the cross-platfotrm space and, so far, the closest to accomplish the stated task has been wX- and IT has it's issues. Most of the time, you end up sacrificing functionality to accomplish the task you're demanding of things. Even wX sacrifices some things to accomplish it's goals there.

Does this mean you should use wX? Perhaps- depends on what you're trying to accomplish. Some things will gain from the support for native UI widgets, some things will explicitly not. You should use the best tool for a specific task and not try to jam something less suited because it meets a tick box item for "native look and feel".