Thanks, Darren - That's a good start, and I can try to follow that.
My first challenge is getting back to the 64 bit python. (By the way, is there
a way to tell, once I have it, whether it is 32 bit or 64 bit?)
Macport sounds like a WONDERFUL idea! I noticed your comments were prefaced
with "
Hi Bruce,
On Fri, Dec 18, 2009 at 4:43 PM, Bruce Anderson wrote:
> I tired the standard instructions from Mark Summerfield's book. Failed - 64
> bit vs 32 bit. I successfully installed a new version of Python (2.6.4),
> the XCode from the install disk, Qt (Carbon, I think - 32 bit?), and SIP.
In case anyone is interested, here is a small python script that fixes the qt
sources to properly finish a debug build after configure is run. This might
save you a couple hours if you need to make debug versions.
It appears that qpycore.lib should be dqpycore.lib and so on but configure
misna
I tired the standard instructions from Mark Summerfield's book. Failed - 64
bit vs 32 bit. I successfully installed a new version of Python (2.6.4), the
XCode from the install disk, Qt (Carbon, I think - 32 bit?), and SIP. Only
PyQt failed.
Then I found Darren Dale's note from Dec 2nd and t
On Fri, Dec 18, 2009 at 6:26 PM, Oliver Heyme wrote:
> Now we where looking into the subject of having an embedded scripting
> language in the Qt C++ app and Python + PyQt + sip would be perfect.
>
> Now we are not sure about the license.
If you think the users may want to distiribute their scr
> If you are not using PyQt you can release your application under LGPL.
>
> Sip license seems to allow that if I have properly understood it:
>
> http://www.riverbankcomputing.co.uk/software/sip/license
>
> If I have misunderstood it the rest of my mail will be senseless.
>
> At the moment you or
Hi Oliver,
Oliver Heyme wrote:
Well the C++ app will be released under LGPL!
And you are saying that this than also is binding for the Python script we
deliver with the app!?!?!
Even though we distribute them as source code and anybody can freely change and
use them?!?!
If you are not us
On Fri, 18 Dec 2009 17:44:32 +0100, Oliver Heyme
wrote:
> Well the C++ app will be released under LGPL!
>
> And you are saying that this than also is binding for the Python script
we
> deliver with the app!?!?!
Yes.
> Even though we distribute them as source code and anybody can freely
change
>
Well the C++ app will be released under LGPL!
And you are saying that this than also is binding for the Python script we
deliver with the app!?!?!
Even though we distribute them as source code and anybody can freely change and
use them?!?!
Oli
On 18.12.2009, at 17:34, Phil Thompson wrote:
> O
On Fri, 18 Dec 2009 17:26:01 +0100, Oliver Heyme
wrote:
> Hej,
>
> We are currently investigating the foundation for an application we start
> to develop beginning next year!
> It will be a mostly internally used software but we are planning to give
it
> out for free to some partners!
>
> So, we
Hej,
We are currently investigating the foundation for an application we start to
develop beginning next year!
It will be a mostly internally used software but we are planning to give it out
for free to some partners!
So, we already have chosen Qt with the LGPL for the application since we don'
On Freitag, 18. Dezember 2009, Phil Thompson wrote:
> On Fri, 18 Dec 2009 15:34:19 +0100, detlev
>
> wrote:
> > Hi,
> >
> > how do I port code like
> >
> l="hh"
> t=app.translate("Test", "s - %1 - e").arg(l)
> >
> > to the QString API version 2? I need to have the relocatable
>
> place
On Fri, 18 Dec 2009 15:34:19 +0100, detlev
wrote:
> Hi,
>
> how do I port code like
>
l="hh"
t=app.translate("Test", "s - %1 - e").arg(l)
>
> to the QString API version 2? I need to have the relocatable
placeholders.
Use Python's...
t = app.translate("Test", "s - {0} - e").forma
Hi,
how do I port code like
>>> l="hh"
>>> t=app.translate("Test", "s - %1 - e").arg(l)
to the QString API version 2? I need to have the relocatable placeholders.
Regards,
Detlev
--
Detlev Offenbach
det...@die-offenbachs.de
___
PyQt mailing listP
Phil Thompson-5 wrote:
>
>>I had to replace
>> ImageLink arguments in signal definition with 'PyQt_PyObject', not sure
>>why exactly)
>
> Neither am I.
>
Else I would get the following message:
> TypeError: type 'classobj' is not supported as a pyqtSignal() type
> argument type
>
which is
Hello all,
I just started learning pyqt and it's been nice.. When i'm experimenting
with the tabbar i encountered this.. As a minimal example i want to show a
button in tab1 and a label in tab2.. Here's what i did
from PyQt4 import QtGui
class Ui_TabWidget(QtGui.QTabWidget):
def __init__(self
16 matches
Mail list logo
