DerLeiter
Member-
Content count
5 -
Joined
-
Last visited
Posts posted by DerLeiter
-
-
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.
-
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.
-
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
-
I've already started a port of LinuxDC++ to Qt and I intend to make it cross-platform. Preliminary results can be seen here : http://onyxdc.sourceforge.net/
We already have Qt based DC++ client - EiskaltDC++ (http://code.google.com/p/eiskaltdc/). There is ChangeLog
We're porting to Linux: and paying!
in Client Discussion
Posted
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.