Re: [PyQt] KAboutData() broken when using PyQt 4.4
Adeodato Simó wrote: Hello, I upgraded to PyQt 4.4.2 this morning, and now KAboutData no longer works for me: How did you upgrade and this which version of PyKDE4 are you using? and how did you install PyKDE4. While working on the PyKDE 4.1 I came across a build problem which happen if PyQt 4.4 is used. The symptoms were rather confusing. This was the fix: http://websvn.kde.org/?view=revrevision=812575 cheers, -- Simon Edwards | KDE-NL, Guidance tools, Guarddog Firewall [EMAIL PROTECTED] | http://www.simonzone.com/software/ Nijmegen, The Netherlands | ZooTV? You made the right choice. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] KAboutData() broken when using PyQt 4.4
* Jim Bublitz [Sat, 14 Jun 2008 14:00:27 -0700]: It works here with Qt 4.3/PyQt 4.3.3/sip 4.7.4/KDE 4.0.2/PyKDE 4.0.2. Right, it is without doubt related to PyQt, because upgrading that is what caused the problem. This is my last *working* state: sip - 4.7.6 Qt - 4.4.0 PyQt - 4.3.3 -- note this KDE - 4.0.80 PyKDE4 - 4.0.2 (from Riverbank) If I upgrade PyQt to 4.4.2, things stop working. Also note how running PyQt 4.3 against Qt 4.4 works, and PyKDE4 against KDE 4.0.80 too. I doubt there's been a change in KDE (you don't indicate a version), so it's likely there's some change in sip or PyQt that's causing the problem. I'll have to upgrade to troubleshoot it, and that may take me a while to get to. So, Jim, sounds like a change in PyQt, yes. No idea if this could be related to the fix Simon mentions or not. Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org He who has not a good memory should never take upon himself the trade of lying. -- Michel de Montaigne ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Problem using class template
Hi I'm having problems wrapping an instantiation of a class template with SIP. I've attached a case that shows what I am trying to do. The class template is defined in base.sip, and an instantiation (through a typedef in another class) is defined in case.sip. The case is built by first running configure-sip.py and then make. The SIP step succeeds, but compiling the result fails due to a missing function 'sipNm_case_getObject'. Is this due to a bug in SIP, or am I doing something wrong? Thanks, Arve case.tar Description: Unix tar archive ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Re: Template - unsupported function return type
On 6/13/08, Matt Newell [EMAIL PROTECTED] wrote: On Friday 13 June 2008 08:04:46 Arve Knudsen wrote: Looks like I made it work, somehow. Anyway, I refer to the class template in the SIP specification using a typedef. That leads to another problem, however. The generated code refers to the typedef, but lacks its definition. How do I include the header containing the typedef?? For a class I would use %TypeHeaderCode, but can't see anyway of doing the same for typedefs .. %ModuleHeaderCode #include myheader.h %End Thanks for the tip. Arve ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] ANN: new eric 4.2 snapshot available
Hi, I'd like to inform everybody about the immediate availability of a new eric 4.2 snapshot. It fixes a few bugs and includes these changes. - compatibility fix for Ubuntu and Mandriva - added the relocate action to the vcsSubversion plugin - added an action to insert a new line below the current one (Shift+Return) - added a QWebKit based help viewer (available if Qt 4.4 is installed) - made some network related aspects configurable - added storage key PROJECTTYPESPECIFICDATA for project type specific data (may be used by project type plugins) - made Shell history more comfortable by -- selecting from history via a dialog -- list the history in a dialog with capabilities to --- delete entries --- copy entries to the current editor --- execute entries in the shell - made the size grip of the main window configurable (s. Interface (Part 1)) It is available via http://www.die-offenbachs.de/eric/snapshots4. Regards Detlev -- Detlev Offenbach [EMAIL PROTECTED] ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] KAboutData() broken when using PyQt 4.4
Adeodato Simó wrote: * Jim Bublitz [Sat, 14 Jun 2008 14:00:27 -0700]: It works here with Qt 4.3/PyQt 4.3.3/sip 4.7.4/KDE 4.0.2/PyKDE 4.0.2. Right, it is without doubt related to PyQt, because upgrading that is what caused the problem. This is my last *working* state: sip - 4.7.6 Qt - 4.4.0 PyQt - 4.3.3 -- note this KDE - 4.0.80 PyKDE4 - 4.0.2 (from Riverbank) If I upgrade PyQt to 4.4.2, things stop working. Also note how running PyQt 4.3 against Qt 4.4 works, and PyKDE4 against KDE 4.0.80 too. So, Jim, sounds like a change in PyQt, yes. No idea if this could be related to the fix Simon mentions or not. Did you recompile PyKDE4 against the new version of PyQt4? When recompiling PyKDE4, did it see that PyQt 4.4 was being used? cheers, -- Simon Edwards | KDE-NL, Guidance tools, Guarddog Firewall [EMAIL PROTECTED] | http://www.simonzone.com/software/ Nijmegen, The Netherlands | ZooTV? You made the right choice. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] KAboutData() broken when using PyQt 4.4
* Simon Edwards [Sun, 15 Jun 2008 15:07:28 +0200]: sip - 4.7.6 Qt - 4.4.0 PyQt - 4.3.3 -- note this KDE - 4.0.80 PyKDE4 - 4.0.2 (from Riverbank) If I upgrade PyQt to 4.4.2, things stop working. Also note how running PyQt 4.3 against Qt 4.4 works, and PyKDE4 against KDE 4.0.80 too. So, Jim, sounds like a change in PyQt, yes. No idea if this could be related to the fix Simon mentions or not. Did you recompile PyKDE4 against the new version of PyQt4? When recompiling PyKDE4, did it see that PyQt 4.4 was being used? No, I didn't, and I really hope the answer is not You need to. -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Listening to: Mastretta - Última vuelta en Monmeló ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Re: RAD with PyQt?
David == David Boddie [EMAIL PROTECTED] writes: David On Thu Jun 12 11:11:46 BST 2008, Alberto Berti wrote: I forgot to mention that: dev news are at http://www.pypapi.org/rdg/timeline and source code and changes browser is at http://www.pypapi.org/rdg/browser . David Does this project share some of the same goals as PyDADL? David http://pydadl.sourceforge.net/ Not really, from what i can say looking at PyDADL's tutorial, it is a framework for building rich xml clients, with a runtime that marshalls and unmarshalls data and events to http/xml, with gui composed by customized widgets. It's sort of a web application framework which uses a runtime different from standard browsers. Compared to this, PyPaPi is an application framework in a more classic meaning. Its role is to make standard python objects hierarchies viewable and editable using standard Qt widgets, the same you use to build forms in Qt Designer (really, Qt Designer _is the preferred way_ to build forms in PyPaPi). PyPaPi then goes further and offers support and more features if your objects are persisted using SQLAlchemy (it then supports a wide range of RDBMS backends). In PyPaPi, an application is a standard pyqt application, which runs on the client with (if needed) a classic db connection (it is not three tier), the only xml used are for form description (.ui files made by designer) and for configuration syntax. Our thoughts are that with modern vpn technologies, all the xml rich clients fashion loses most of it's meaning, and we do love writing python, not xml. For who asked for pypapi docs, i'm preparing a tutorial (still to be finished) that shows some PyPaPi features: it's here http://www.pypapi.org/rdg/browser/docs/cute/tutorial/README.rst any comment is welcome:) Alberto ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Problem using class template
On Sunday 15 June 2008 10:57:08 am Arve Knudsen wrote: Hi I'm having problems wrapping an instantiation of a class template with SIP. I've attached a case that shows what I am trying to do. The class template is defined in base.sip, and an instantiation (through a typedef in another class) is defined in case.sip. The case is built by first running configure-sip.py and then make. The SIP step succeeds, but compiling the result fails due to a missing function 'sipNm_case_getObject'. Is this due to a bug in SIP, or am I doing something wrong? Thanks, Arve Hopefully fixed in tonight's snapshot. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] KAboutData() broken when using PyQt 4.4
On Sunday 15 June 2008 06:36, Adeodato Simó wrote: * Simon Edwards [Sun, 15 Jun 2008 15:07:28 +0200]: sip - 4.7.6 Qt - 4.4.0 PyQt - 4.3.3 -- note this KDE - 4.0.80 PyKDE4 - 4.0.2 (from Riverbank) If I upgrade PyQt to 4.4.2, things stop working. Also note how running PyQt 4.3 against Qt 4.4 works, and PyKDE4 against KDE 4.0.80 too. So, Jim, sounds like a change in PyQt, yes. No idea if this could be related to the fix Simon mentions or not. Did you recompile PyKDE4 against the new version of PyQt4? When recompiling PyKDE4, did it see that PyQt 4.4 was being used? No, I didn't, and I really hope the answer is not You need to. Unfortunately, you do need to recompile PyKDE any time you change sip or PyQt versions. I wouldn't guarantee that will fix the problem, but it's a first step. Jim ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
