How is GUI programming in Python?
steve at holdenweb.com
Fri Apr 11 01:01:43 CEST 2008
Michel Bouwmans wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Mike Driscoll wrote:
>> On Apr 10, 12:05 pm, Michel Bouwmans <mfb.chikaz... at gmail.com> wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>> Paul Rubin wrote:
>>>> Chris Stewart <cstewart... at gmail.com> writes:
>>>>> I've always had an interest in Python and would like to dabble in it
>>>>> further. I've worked on a few very small command line programs but
>>>>> nothing of any complexity. I'd like to build a really simple GUI app
>>>>> that will work across Mac, Windows, and Linux. How painful is that
>>>>> going to be? I used to be really familiar with Java Swing a few years
>>>>> ago. I imagine it will be similar.
>>>>> Next, what would you say is the best framework I should look into?
>>>> If by "best" you mean "easiest", that is probably tkinter, which
>>>> comes with python. It is somewhat rudimentary and the widgets that
>>>> come with it don't look so great. But if you just want to put up
>>>> GUI's with basic functionality and not much glitz, it is ok for most
>>>> such purposes.
>>>> out how to use
>>> I don't quite agree with you on this. Tkinter may be easy because it is
>>> available by standard in Python, but that's about it in my opinion. The
>>> API, look and performance hit is horrible. You're much better of with
>>> PyQt4 which makes the job really simple.
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.7 (GNU/Linux)
>>> -----END PGP SIGNATURE-----
>> I see a lot of people recommend using pyQt, but they never mention the
>> controversy that surrounds its licensing. There have been many posts
>> on the subject already, but if the OP ever decides to sell anything
>> they create, I've heard that QT's licensing is kind of squirrelly.
>> Maybe this has been straightened out?
>> I looked at the website and found it fairly confusing. And don't you
>> need to download QT itself?
> Yeah, the licensing of Qt is either be open-source (under one of the
> Qt-exception licenses licenses so no exclusivity for the GPL anymore) or
> pay for the commercial version. So yes, if you would like to sell it as
> closed-source software you will need to buy the commercial version of Qt
> and PyQt. In other words: you will have to pay twice. Don't forget that you
> can also sell open-source software, so you don't have to pay. ;)
I don't think PyQt has any licensing restrictions to speak of, only the
underlying Qt platform (though it's a while since I looked).
Steve Holden +1 571 484 6266 +1 800 494 3119
Holden Web LLC http://www.holdenweb.com/
More information about the Python-list