Salman Khilji <skhilji@tampabay.rr.com> [Sat, 21 Jun 2003 13:15:26 -0700]:

WRONG!!!!!! wxWindows is C++ based! Its GTK that you are confusing it with which is, of course, C based.

Yes you're right, I did mix up the two. Thanks for correcting me.

wxWindows uses MFC based design paradigm. However, the design of wxWindows (again in my opinion) is at least somewhat better than MFC. Still nothing compared to Qt.

Does wxWindows still make heavy use of macros for creating classes instead of using templates? Philipp

Salman Khilji <skhilji@tampabay.rr.com> [Sat, 21 Jun 2003 15:47:30 -0700]:

it does not use macros to "create classes". And "creating classes" would not requier templates.

Forgive me, English isn't my native tongue. What I meant is instantiating classes via macros. Like list<int> but done via macro, is that clearer? AFAIR there was code like that in wxWindows the last time I checked (must be 2 years ago). Philipp

On Saturday 21 June 2003 22:12, Salman Khilji wrote:

if its a free tool, then Qt is not your choice since the Windows version is not free (and according to some people not GPL compatible).

AFAIK the windows version of Qt 2.x _is_ released under the exact same dual-license (GPL/QPL?), thus free to use as long as your app is GPL'ed. Point is, this only holds for a specific 2.x version, while it does not hold for any 3.x version. Regards, -- tinus ___________________________________________________ "Words are weightless here on earth Because they're free." -- Josh Homme

On Monday 23 June 2003 01:32, Martijn Houtman wrote:

On Saturday 21 June 2003 22:12, Salman Khilji wrote:

...

if its a free tool, then Qt is not your choice since the Windows version is not free (and according to some people not GPL compatible).

AFAIK the windows version of Qt 2.x _is_ released under the exact same dual-license (GPL/QPL?), thus free to use as long as your app is GPL'ed. Point is, this only holds for a specific 2.x version, while it does not hold for any 3.x version.

That is not correct. The Windows version of Qt-2.3 was released under a non-commercial licence, which is much more restrictive than the GPL and doesn't come with source. The experiment was a failure. Trolltech discovered that a lot of people were breaking the licence and developing commercial software with it, so they decided not to release any more versions under the Qt-NCL. That version of Qt is still widely used though, because it was the most mature of the 2.x series and still works really well. -- "...our desktop is falling behind stability-wise and feature wise to KDE ...when I went to Mexico in December to the facility where we launched gnome, they had all switched to KDE3." - Miguel de Icaza, March 2003

* Remo Behn <ray@suse.de> [030623 08:50]:

* Praise <praisetazio@tiscalinet.it> [030620 21:08]:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi all,

I will be starting a project for a multi-platform chat client within a month. Supported platforms will be Linux and Windows. I thought I was going to use qt, when I discovered the free wxwindows. So here it is my question: apart from license, what is better? qt or wxwindows? Just looking for your experiences and thoughts.

Praise -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE+81ui6v3ZTabyE8kRAvDGAKDRtLLSOTmKdANU7+1qBEyayTeC3gCdGW+M iYwtaJeP6Q3YjpqmN1lIP1g= =0jQB -----END PGP SIGNATURE-----

use perl-qt from this site

http://perlqt.sourceforge.net/

!!!!!!!!!! is for qt3 !!!!!!!!!!

on suse linux 8.2 install perl-Qt package und have fun look documentation: /usr/share/doc/packages/perl-Qt/tutorials /usr/share/doc/packages/perl-Qt/examples

small supplement ... you can user trolltech qt designer for draw the gui look "puic --help" puic -x -p 4 -o test.pl test.ui cu -- echo '@a=(A..Z,a..z," ");$t="a"x16;{for($x=0,$|=$n=30; $n--;){for($l=$t; 1<rand 7;) {substr$l,rand 16,1,$ a[rand@a]}$q=$_="znurB ehT naMyaR";for($a=$l; $_;){s/.//;$q++ if chop$a eq$&}if($x<=$q){$e=$l;die$ e,$/if($x=$q)==16}} print$t=$e,"\r";redo}'|perl

I had some experience trying to get one of the software that used PyQt. first you had to have a particular version of Qt. Then a particular version of PyQt. If the version of PyQt did not like the version of the installed Qt libraries, you had a problem.

I tried several combinations and at the end could never get the program to run. Anyways, if I had spent only about ten thousand more hours on it, maybe I could get it to run.

So again, if you use Qt only and make it statically linked, chances are that you won't get into trouble with layers and layers over one another.

Any binary compatible version should work, and Trolltech are good at making their major releases binary compatible. Your PyQt problem is more likely to be the well known SuSE issue than anything to do with Qt. Mind you, I agree with your underlying point: PyQt is excellent; PerlQt, er, isn't. :o) -- "...our desktop is falling behind stability-wise and feature wise to KDE ...when I went to Mexico in December to the facility where we launched gnome, they had all switched to KDE3." - Miguel de Icaza, March 2003