On Thursday 17 February 2005 19:39, Paul Giannaros wrote:
> Hey
> I've been looking for information on connecting to DCOP and providing
> methods accessible over DCOP.
> I take it from what i've read in the mailing list archives and from what
> docs I could find on the subject such functionality
Ulrich Berning <[EMAIL PROTECTED]> wrote:
> Using from ... import * in normal code is (and was) always a bad
> idea. I have avoided it whenever possible. You pollute your local
> namespace with
> all names from the imported modules and name clashes are are likely to
> occur.
You probably did not
Hey
I've been looking for information on connecting to DCOP and providing methods
accessible over DCOP.
I take it from what i've read in the mailing list archives and from what docs
I could find on the subject such functionality is not available in pyKDE?
More specifically, is there a way to do
On Thu, 17 Feb 2005 16:59:53 - (GMT)
"Phil Thompson" <[EMAIL PROTECTED]> wrote:
[ .. ]
>
> >> A self-installing
> >> binary package, with the Qt libraries statically linked
> >
> > Is there a reason for being statically linked? Thats a complication for
> > third
> > party python modules that
Giovanni Bajo schrieb:
Just one personale note: right now, I usually do:
from qt import *
because I find it useless to write "qt.QApplication" instead of
"QApplication" since the leading uppercase "Q" is already a kind of
namespace, which is imposed by qt itself. If (by absurd) the class was named
Hi!
I'm trying to populate a new toolbar in a form in Qt Designer, but I can't
because the only option that I find pressing the right button on the new
toolbar is to delete the toolbar. How can be done?
Thanks!
David Gil
--
Visita jorge.cortell.net
Encrypted mail preferred (PGP KEY 0xCBDF3315
On Thu, 17 Feb 2005 18:56:13 -0300
Nahuel Greco <[EMAIL PROTECTED]> wrote:
> Now I have the equivalent program done in C++ and PyQT, and the C++ one
> don't leak but the PyQT one keeps leaking. I'm attaching the new version
> of both and their output.
>
Note, the PyQT program leaks also when in
On Thu, 17 Feb 2005 17:03:16 - (GMT)
"Phil Thompson" <[EMAIL PROTECTED]> wrote:
> Gentoo (x86 and amd64). I didn't run the C++ test - I was refering to the
> original Python test that Torsten sent me.
Ok, I was confused because I tought that you were having different results
with the C++ test
We've built Eric 3.6.1 on Solaris 2.6-9/SPARC, HP-UX 11.x, Tru64 UNIX
5.1, IRIX 6.5, AIX 5.x, and RHEL 3.0. At the least, the main window
comes up :)
In the main window, a section is devoted to a Python session. We see
the following:
1 Python 2.3.5 (No.1, Feb 9 2005, 12:01:46)
2 [GCC 3.4.3 (
On Thu, 17 Feb 2005 15:22:26, Phil Thompson wrote:
> The separate Qt v4 libraries will be wrapped as separate Python modules.
> The module names will be the same as the corresponding library (eg.
> QtCore, QtGui) and be grouped as a single Python package called PyQt4. The
> suggested programming s
On Thursday 17 February 2005 19:22, Hans-Peter Jansen wrote:
>
> BTW, both SuSE 9.0 and 9.2 leaks like hell with your c++ test..
> Qt 3.3.4 still compiling ;-)
and did it only slightly better (-10MB at 10 dialogs: still 151 MB
compared to 3.2.1)
Pete
Hi Nahuel,
On Thursday 17 February 2005 17:32, Nahuel Greco wrote:
> On Thu, 17 Feb 2005 12:56:57 - (GMT)
>
> "Phil Thompson" <[EMAIL PROTECTED]> wrote:
> > > Do you tried the previous test program with Qt 3.3.4?
> >
> > Yes.
>
> I tried with Qt 3.3.4 and I have the same problem, and every per
On Thursday 17 February 2005 08:30, Phil Thompson wrote:
> > Phil Thompson <[EMAIL PROTECTED]> wrote:
> >> The separate Qt v4 libraries will be wrapped as separate Python modules.
> >> The module names will be the same as the corresponding library (eg.
> >> QtCore, QtGui) and be grouped as a single
> On Thu, 17 Feb 2005 12:56:57 - (GMT)
> "Phil Thompson" <[EMAIL PROTECTED]> wrote:
>
>> > Do you tried the previous test program with Qt 3.3.4?
>>
>> Yes.
>
> I tried with Qt 3.3.4 and I have the same problem, and every person I know
> with a Debian distribution and Qt 3.3.3 have the same erro
> On Thursday 17 February 2005 15:22, Phil Thompson wrote:
>> I've put up a short roadmap for PyQt v4 on the website, and the text is
>> below. Any comments welcome.
>
> That looks great.
>
>> A GPL version of PyQt for Windows will be supported.
>
> You dont say it, but I assume the commercial vers
On Thursday 17 February 2005 15:22, Phil Thompson wrote:
> I've put up a short roadmap for PyQt v4 on the website, and the text is
> below. Any comments welcome.
That looks great.
> A GPL version of PyQt for Windows will be supported.
You dont say it, but I assume the commercial version will be
On Thu, 17 Feb 2005 12:56:57 - (GMT)
"Phil Thompson" <[EMAIL PROTECTED]> wrote:
> > Do you tried the previous test program with Qt 3.3.4?
>
> Yes.
I tried with Qt 3.3.4 and I have the same problem, and every person I know
with a Debian distribution and Qt 3.3.3 have the same error, so maybe
> Phil Thompson <[EMAIL PROTECTED]> wrote:
>
>> The separate Qt v4 libraries will be wrapped as separate Python modules.
>> The module names will be the same as the corresponding library (eg.
>> QtCore, QtGui) and be grouped as a single Python package called PyQt4.
>> The
>> suggested programming s
Agreed... But we are supporting a large body of code that already has
many "import qt" and "from qt import *" statements throughout the
code... Having a more standardized way of handling this (rather than
providing a 'qt.py' file for every project that uses pyqt) would be
much preferrable...
Phil Thompson <[EMAIL PROTECTED]> wrote:
> The separate Qt v4 libraries will be wrapped as separate Python modules.
> The module names will be the same as the corresponding library (eg.
> QtCore, QtGui) and be grouped as a single Python package called PyQt4. The
> suggested programming style for n
On Thu, Feb 17, 2005 at 08:05:49AM -0800, Longson, Joe wrote:
> >The separate Qt v4 libraries will be wrapped as separate Python modules.
> >The module names will be the same as the corresponding library (eg.
> >QtCore, QtGui) and be grouped as a single Python package called PyQt4. The
> >suggested
Would we be required to use the from PyQt4 import QtGui?
The existing namespace allows us to do "import qt" Could a similar
facility be provided? (for maintaining more code compatibility)
e.g.
In qt.py --
from PyQt4 import *
from PyQt4.QtGui import *
...
Then we could do something li
Phil Thompson wrote:
I've put up a short roadmap for PyQt v4 on the website, and the text is
below. Any comments welcome.
Phil
Very good news. I applaud your decision
and your continuing commitment to PyQt.
Thanks
___
PyKDE mailing listPyKDE@mats.imk.
I've put up a short roadmap for PyQt v4 on the website, and the text is
below. Any comments welcome.
Phil
PyQt v4 will support Qt v4 only. It will not support earlier versions of
Qt in the way that PyQt v3 supports Qt v1 to v3. PyQt v3 will continue to
be supported.
PyQt v4 will require SIP v4.
> On Thu, 17 Feb 2005 09:24:36 - (GMT)
> "Phil Thompson" <[EMAIL PROTECTED]> wrote:
>
>> Qt 3.3.4 from Trolltech.
>
> Ok, maybe this is a problem related to Qt 3.3.3, I will try using Qt
> 3.3.4.
>
> Do you tried the previous test program with Qt 3.3.4?
Yes.
> There where no
> leaks?
I don't
On Thu, 17 Feb 2005 09:24:36 - (GMT)
"Phil Thompson" <[EMAIL PROTECTED]> wrote:
> Qt 3.3.4 from Trolltech.
Ok, maybe this is a problem related to Qt 3.3.3, I will try using Qt 3.3.4.
Do you tried the previous test program with Qt 3.3.4? There where no leaks?
Saludos,
Nahuel Greco.
__
> On Wed, 16 Feb 2005 15:00:52 - (GMT)
> "Phil Thompson" <[EMAIL PROTECTED]> wrote:
>
>> What version of Qt are you using? There was some talk of the Debian
>> version of Qt leaking memory.
>
> I'm using the latest Qt-mt library from Debian unstable, 3.3.3
> (3:3.3.3-8).
> What version are you
In fact the exception message is "correct". When there are overloaded
functions or ctors, none of which have a matching signature, then there is
a (potentially) different exception message for each one. SIP then has to
choose the most appropriate one. It's impossible to get this right
(without read
> Message: 7
> Date: Wed, 16 Feb 2005 09:05:23 - (GMT)
> From: "Phil Thompson" <[EMAIL PROTECTED]>
> Subject: Re: [PyKDE] sip undefined type
> To: "jim" <[EMAIL PROTECTED]>
> Cc: pykde@mats.imk.fraunhofer.de
> Message-ID:
> <[EMAIL PROTECTED]>
> Content-Type: text/plain;charset=iso-8859
29 matches
Mail list logo
