On Monday 11 September 2006 11:47, Simon Edwards wrote:
> Then if I have a KDE program PyFoo that includes a Python C module (or sip
> wrapper) and was developed for KDE 4.0, it will called something PyFoo2.5
> and require KDE 4.0 or later. When KDE 4.1 comes out maybe Python 2.6 is
> also out, but
On Monday 11 September 2006 21:29, Andreas Pakulat wrote:
> That's not quite true anymore, at least for Etch and onwards you'll only
> have
> python-qt3
> which provides pyqt3 for python2.4 and 2.3 (atm, but possibly also 2.5).
> I don't know how this new python policy works, but that is what hap
On Monday 11 September 2006 08:42, Andreas Pakulat wrote:
> On 10.09.06 21:41:28, Dave S wrote:
> > I SOLVED it :)
> >
> > OK it took me 8 straight hours of hitting head on keyboard but ...
> >
> > def main(args):
> >
> > app = QApplication(args)
> > docview = View()
> > docvie
On 11.09.06 20:47:31, Simon Edwards wrote:
> On Saturday 09 September 2006 16:36, Phil Thompson wrote:
> > On Friday 08 September 2006 8:46 pm, Simon Edwards wrote:
> > > What we want to be able to tell users and 3rd party developers is that a
> > > KDE 4.0 application written in Python will work f
On Saturday 09 September 2006 16:36, Phil Thompson wrote:
> On Friday 08 September 2006 8:46 pm, Simon Edwards wrote:
> > What we want to be able to tell users and 3rd party developers is that a
> > KDE 4.0 application written in Python will work fine on any 4.0+ version
> > of
> > KDE, just like
On 10.09.06 21:41:28, Dave S wrote:
> I SOLVED it :)
>
> OK it took me 8 straight hours of hitting head on keyboard but ...
>
> def main(args):
>
> app = QApplication(args)
> docview = View()
> docview.parent = docview
> app.setMainWidget(docview)
> docview.show()
>
In this way works. Thank you so much Andreas, you've saved my life...2006/9/8, Andreas Pakulat <[EMAIL PROTECTED]>:
On 08.09.06 16:29:32, Oscar Cossu wrote:>def child(self, i):>if self.childItems.has_key(i):>return self.childItems[i]>>if i >= 0 and i < self.domNode.c
