DerLeiter

Member
  • Content count

    5
  • Joined

  • Last visited

Posts posted by DerLeiter


  1. Here is one of the reasons: for example I want to make some Qt-based software look exactly like any other app on my GNOME distro. In order to install it I must first install lots of Qt libraries to make it just work and look like an alien on my system/ What should I do? I should find where to download one small package qgtkstyle which is not in official repo and I should waste my time to find it somewhere in the internet. So in order not to waste lots of time I'll find some app which is providing the same functions drawing all the controls natively without harmonious system of crutches and props and without dancing with the tambourine around my computer

    You must have been lucky making it all work as I've seen a Qt project (not very difficult, written on Windows, using only Qt and standard C functions) which gave about 70 errors during compiling on Linux with the same version of Qt/

    First, you need qtcurve-gtk/-qt for uniform look GTK and Qt programs, second, in KDE-based distros all GTK-based programs (wxWidgets uses GTK) looks ugly without "dancing with the tambourine" (installing qtcurve), therefore your example with GNOME is wrong. In any case, I want to offer assistance with porting ApexDC++ on Linux.


  2. Yeah but the difference to wxwidgets is this:

    ...

    That comes straight from wxwidgets wiki so it might be that the info is bit dated but I believe still valid.

    I do not understand the reason for which you need precisely native controls on each platform... I use Qt for writing my programs that runs on Linux, Windows and Mac OS X and never had a situation where I needed a native controls on each platform.


  3. I have nothing particularly against Qt but my reasons for favoring wxWidgets is that it can look 100% native on windows (which until proven otherwise is the majority of our userbase).

    Qt 4.6 uses native styles for drawing controls on each operating system such as Mac OS X or Windows.


  4. but this text doesn't specify the license version. It is only pure copy of statement from FSF. Important thing is "or (AT YOUR OPTION) any later version", but, according to license.txt, this option hasn't been selected.

    License specified in source code has a higher priority than the license specified in file LICENSE. So EiskaltDC++ has no problems with licenses. Details