On Saturday 04 December 2004 10:30 am, Michael Sparks wrote:
> On Fri, 3 Dec 2004, Phil Thompson wrote:
> ...
>
> > The key is access to the Qt API. If your applications gives the users
> > access to the API then those users are developers and need their own
> > licenses. On the other hand if the A
On Fri, 3 Dec 2004, Phil Thompson wrote:
...
> The key is access to the Qt API. If your applications gives the users access
> to the API then those users are developers and need their own licenses. On
> the other hand if the API is sufficiently removed from the Qt API then you
> shouldn't have a pr
On Friday 03 December 2004 2:50 pm, Fabio wrote:
> Hi all,
> I'm about to write an application, and I'd like to use PyQt, but before
> choosing this toolkit I would like to clarify some particular licensing
> issues; if some user has already touched these, I would like to hear from
> his experience
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PyQt on OS X is also available under a GPL version. I have a binary
installer available at http://www.wordtech-software.com/pyqt-mac.html
Fabio wrote:
| Hi all,
| I'm about to write an application, and I'd like to use PyQt, but before
| choosing this t
Fabio wrote:
I'm about to write an application, and I'd like to use PyQt, but before
choosing this toolkit I would like to clarify some particular licensing
issues; if some user has already touched these, I would like to hear from
his experiences.
This app should be cross-platform, so, given qt lic
Hi all,
I'm about to write an application, and I'd like to use PyQt, but before
choosing this toolkit I would like to clarify some particular licensing
issues; if some user has already touched these, I would like to hear from
his experiences.
This app should be cross-platform, so, given qt licensi
