Sundance <[EMAIL PROTECTED]> wrote:
>> I like it - except I would use "Qt" rather than "qt". In fact I
>> really, really like it.
>
> Ditto!
>
> Giovanni, say: would that also remove the drawback from your awesome
> static PyQt module project? I looked into the issue of distributing
> easy-to-inst
On Thu, Mar 02, 2006 at 03:15:45PM +, Phil Thompson wrote:
> I like it - except I would use "Qt" rather than "qt". In fact I
> really, really like it.
Ditto!
Giovanni, say: would that also remove the drawback from your awesome
static PyQt module project? I looked into the issue of distribut
On Thursday 02 March 2006 3:43 pm, Sundance wrote:
> On Thu, Mar 02, 2006 at 02:58:18PM +, Phil Thompson wrote:
> > What you describe can be implemented, but it means that the Qt module
> > must be linked against the Core and Gui Qt libraries.
>
> Oookay, you've lost me there. I thought that, w
On Thu, Mar 02, 2006 at 02:58:18PM +, Phil Thompson wrote:
> What you describe can be implemented, but it means that the Qt module
> must be linked against the Core and Gui Qt libraries.
Oookay, you've lost me there. I thought that, with the exception of
convertFromPlainText(), escape() and
On Thursday 02 March 2006 2:38 pm, Gerard Vermeulen wrote:
> On Thu, 2 Mar 2006 15:26:50 +0100
>
> Gerard Vermeulen <[EMAIL PROTECTED]> wrote:
> > I have been wondering for some time if it wouldn't be better to merge
> > QtCore and QtGui into one single module. This resolves the problem of
> > the
On Thursday 02 March 2006 2:45 pm, Sundance wrote:
> On Thu, Mar 02, 2006 at 02:01:35PM +, Phil Thompson wrote:
> > As I said in another reply - I don't see the difference. Whether it's
> > PyQt4.Qt rather than PyQt4.QtCore.Qt, the magic still has to happen
> > when you import QtGui.
>
> Well,
Gerard Vermeulen <[EMAIL PROTECTED]> wrote:
> I have been wondering for some time if it wouldn't be better to merge
QtCore
> and QtGui into one single module. This resolves the problem of the Qt
> namespace clashes. Eventually there could be a QtCore module for people
> who really only need QtCo
On Thursday 02 March 2006 2:26 pm, Gerard Vermeulen wrote:
> On Thu, 2 Mar 2006 12:42:42 +0100
>
> Sundance <[EMAIL PROTECTED]> wrote:
> > On Thu, Mar 02, 2006 at 10:41:45AM +, Phil Thompson wrote:
> > > A C++ namespace doesn't have an implementation, it just contributes to
> > > name mangling.
On Thu, Mar 02, 2006 at 02:01:35PM +, Phil Thompson wrote:
> As I said in another reply - I don't see the difference. Whether it's
> PyQt4.Qt rather than PyQt4.QtCore.Qt, the magic still has to happen
> when you import QtGui.
Well, I think the idea is that the Qt namespace would contain every
On Thu, 2 Mar 2006 15:26:50 +0100
Gerard Vermeulen <[EMAIL PROTECTED]> wrote:
> I have been wondering for some time if it wouldn't be better to merge QtCore
> and QtGui into one single module. This resolves the problem of the Qt
> namespace
> clashes. Eventually there could be a QtCore module f
On Thu, 2 Mar 2006 12:42:42 +0100
Sundance <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 02, 2006 at 10:41:45AM +, Phil Thompson wrote:
>
> > A C++ namespace doesn't have an implementation, it just contributes to
> > name mangling. In Python they have to be implemented by something so
> > there is
On Thursday 02 March 2006 1:20 pm, Giovanni Bajo wrote:
> Phil Thompson <[EMAIL PROTECTED]> wrote:
> >> ---
> >> from PyQt4.QtCore import *
> >> from PyQt4.QtGui import *
> >>
> >> dir(Qt)
> >> ---
> >>
> >> won't show the full Qt namespace, thus maki
On Thursday 02 March 2006 1:52 pm, Sundance wrote:
> Giovanni Bajo wrote:
> > This would be *very* confusing and very implicit. I'm -1000 on this.
>
> Actually, it's more than merely implicit: it's Plain Freaking Magic.
> And magic is dangerous.
>
> I agree that making the Qt namespace a module of
On Thursday 02 March 2006 1:23 pm, Giovanni Bajo wrote:
> Sundance <[EMAIL PROTECTED]> wrote:
> > 1) Having the Qt namespace as an external module.
>
> Perfect. I'm +1 on this.
I don't see how it helps. You've still got one module changing under your feet
when you import another.
>
> > 2) Updati
Giovanni Bajo wrote:
> This would be *very* confusing and very implicit. I'm -1000 on this.
Actually, it's more than merely implicit: it's Plain Freaking Magic.
And magic is dangerous.
I agree that making the Qt namespace a module of its own would be one
darn lot better. What I don't know is wh
Sundance <[EMAIL PROTECTED]> wrote:
> 1) Having the Qt namespace as an external module.
Perfect. I'm +1 on this.
> 2) Updating QtCore.Qt's _dict_ in the other modules instead of
> creating a new Qt there.
This would be *very* confusing and very implicit. I'm -1000 on this.
--
Giovanni Bajo
_
Phil Thompson <[EMAIL PROTECTED]> wrote:
>> ---
>> from PyQt4.QtCore import *
>> from PyQt4.QtGui import *
>>
>> dir(Qt)
>> ---
>>
>> won't show the full Qt namespace, thus making PyQt4 unusable without the
>> annoying QtCore/QtGui prefix in front of
On Thu, Mar 02, 2006 at 10:41:45AM +, Phil Thompson wrote:
> A C++ namespace doesn't have an implementation, it just contributes to
> name mangling. In Python they have to be implemented by something so
> there is no direct comparison.
Point! Although I feel Giovanni does have a point as well
Giovanni Bajo wrote:
> Are you saying that this:
>
> ---
> from PyQt4.QtCore import *
> from PyQt4.QtGui import *
>
> dir(Qt)
> ---
>
> won't show the full Qt namespace, thus making PyQt4 unusable without the
> annoying QtCore/QtGui prefix in front
On 02.03.06 12:09:46, Giovanni Bajo wrote:
> Phil Thompson <[EMAIL PROTECTED]> wrote:
> > Up until recently I had planned (and partially implemented) the idea that
> a
> > namespace would only appear once and that any objects implemented in other
> > modules would be placed in it. In other words...
On Thursday 02 March 2006 11:09 am, Giovanni Bajo wrote:
> Phil Thompson <[EMAIL PROTECTED]> wrote:
> > Up until recently I had planned (and partially implemented) the idea that
>
> a
>
> > namespace would only appear once and that any objects implemented in
> > other modules would be placed in it.
Phil Thompson <[EMAIL PROTECTED]> wrote:
> Up until recently I had planned (and partially implemented) the idea that
a
> namespace would only appear once and that any objects implemented in other
> modules would be placed in it. In other words...
>
> from PyQt4 import QtCore
> dir(QtCore)
> from P
On Thursday 02 March 2006 10:21 am, Sundance wrote:
> On Thu, Mar 02, 2006 at 09:46:03AM +, Phil Thompson wrote:
> > The short answer is that the Python objects are placed in the module
> > corresponding to the C++ library in which they are implemented.
>
> Hmm, meaning that this:
>
> ---[ Code
On Thu, Mar 02, 2006 at 09:46:03AM +, Phil Thompson wrote:
> The short answer is that the Python objects are placed in the module
> corresponding to the C++ library in which they are implemented.
Hmm, meaning that this:
---[ Code snippet ]
On Thursday 02 March 2006 9:59 am, Sreeram Kandallu wrote:
> Phil Thompson wrote:
> > The short answer is that the Python objects are placed in the module
> > corresponding to the C++ library in which they are implemented.
>
> Does this mean that Qt::WindowFlags and such will be moved from
> QtCore
Phil Thompson wrote:
> The short answer is that the Python objects are placed in the module
> corresponding to the C++ library in which they are implemented.
>
Does this mean that Qt::WindowFlags and such will be moved from
QtCore.Qt to QtGui.Qt?
Regards
Sreeram
signature.asc
Description: Ope
On Thursday 02 March 2006 9:07 am, Sreeram Kandallu wrote:
> Hi
>
> I just have a couple of questions regarding conventions that are being
> followed in PyQt4.
>
> I'm using the '20060226' snapshots of PyQt4 and Sip, and i noticed that
> the Qt namespace is present in *both* QtCore and QtGui! why i
Hi
I just have a couple of questions regarding conventions that are being
followed in PyQt4.
I'm using the '20060226' snapshots of PyQt4 and Sip, and i noticed that
the Qt namespace is present in *both* QtCore and QtGui! why is that?
Also, enums like Qt::WindowFlags are present in QtCore.Qt,
whe
28 matches
Mail list logo
