On Tuesday 28 November 2006 15:04, Olaf Schmidt wrote:
> All Qt 4.x release will be binary compatible with earlier Qt 4.y releases,
> so
> couldn't we simply continue using the old bindings if Riverbank should ever
> stop to realise new GPL-licensed Python bindings?
yes,
> If we wish to use fe
On Saturday 25 November 2006 00:30, Phil Thompson wrote:
> That makes no sense at all. You're saying that the situation that the
> agreement covers is if Trolltech continues to develop the commercial version
> but stops developing the GPL version. Which means that the position of
> the "free" co
On Friday 24 November 2006 10:36 pm, Simon Edwards wrote:
> On Friday 24 November 2006 19:04, Phil Thompson wrote:
> > On Friday 24 November 2006 5:37 pm, Simon Edwards wrote:
> > > On Wednesday 15 November 2006 21:12, Simon Edwards wrote:
> > > > Background
> > > > ~~
> > > > The Python bi
On Friday 24 November 2006 19:04, Phil Thompson wrote:
> On Friday 24 November 2006 5:37 pm, Simon Edwards wrote:
> > On Wednesday 15 November 2006 21:12, Simon Edwards wrote:
> > > Background
> > > ~~
> > > The Python bindings consist of a couple of parts. The binding tool SIP
> > > which
On Friday 24 November 2006 10:04, Phil Thompson wrote:
> On Friday 24 November 2006 5:37 pm, Simon Edwards wrote:
> > On Wednesday 15 November 2006 21:12, Simon Edwards wrote:
> > > Background
> > > ~~
> > > The Python bindings consist of a couple of parts. The binding tool SIP
> > > which
On Friday 24 November 2006 5:37 pm, Simon Edwards wrote:
> On Wednesday 15 November 2006 21:12, Simon Edwards wrote:
> > Background
> > ~~
> > The Python bindings consist of a couple of parts. The binding tool SIP
> > which is used to help generate the binding C++ code, PyQt, Python/Qt
> >
On Wednesday 15 November 2006 21:12, Simon Edwards wrote:
> Background
> ~~
> The Python bindings consist of a couple of parts. The binding tool SIP which
> is used to help generate the binding C++ code, PyQt, Python/Qt bindings
> which
> use SIP. Both are produced by Phil Thompson at R
