[PyKDE] Speeing up source file creation when using SIP with PyQt/PyKDE
I'm creating bindings for a module in KDE (not included in PyKDE). While things work fine, running sip on the .sip file takes a long time on my machine -- ~15 seconds. It looks like it's processing all of the Qt/KDE sip stuff each time. I don't fully understand the sip system, but is there a way I can stop it doing so, and just process my single one? None of the arguments to `sip` look promising, neither does a quick search of the documentation help. ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Speeing up source file creation when using SIP with PyQt/PyKDE
On Tuesday 20 February 2007 2:28 pm, Paul Giannaros wrote: I'm creating bindings for a module in KDE (not included in PyKDE). While things work fine, running sip on the .sip file takes a long time on my machine -- ~15 seconds. It looks like it's processing all of the Qt/KDE sip stuff each time. I don't fully understand the sip system, but is there a way I can stop it doing so, and just process my single one? None of the arguments to `sip` look promising, neither does a quick search of the documentation help. You could %Import only the specific .sip files you need - but you'll probably end up %Importing most of them anyway. 15 seconds isn't very long. Phil ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Speeing up source file creation when using SIP with PyQt/PyKDE
On Tuesday 20 February 2007 06:28, Paul Giannaros wrote: I'm creating bindings for a module in KDE (not included in PyKDE). While things work fine, running sip on the .sip file takes a long time on my machine -- ~15 seconds. It looks like it's processing all of the Qt/KDE sip stuff each time. I don't fully understand the sip system, but is there a way I can stop it doing so, and just process my single one? None of the arguments to `sip` look promising, neither does a quick search of the documentation help. You're right - it is processing all of the Qt and KDE stuff that you import. For example, if you have classes (which you almost certainly do) that subclass QObject or QWidget, their header/sip files contain only the information about the methods that the class's new methods or the inherited methods that it overloads. However, when you use the new class, you expect to be able to access any method inherited from QObject or QWidget, so sip has to generate bindings (within the new class) for all of those methods as well, and to do that, it needs to know what those methods are - exactly the same as gcc/g++ needing to see qobject.h, etc. Jim ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] KTextEditor bindings
I've created (almost complete) SIP bindings for the KTextEditor interface. There are a couple of classes that I failed to wrap because of compile errors, but it's mostly there. Would the .sip files be of use to anyone? ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
