[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyKDE] PyQt C API
From:       James Emerton <ephelon () gmail ! com>
Date:       2005-10-20 0:36:02
Message-ID: c9424d940510191736m56a5a574j42f7575e4b88a29a () mail ! gmail ! com
[Download RAW message or body]

> This is the inner loop of the rendering code for a custom graph widget. The
> optimisation target isnt the PyQt code itself, but rather the next layer up,
> which calls PyQt. It will be much more convenient for this C (or C++, or
> pyrex) code to call the Qt C++ API directly.

Now, I've never touched Pyrex, so my understanding here may be a little wonky.

I think you should be able to accomplish the same thing with
straight-up SIP, and reduce the number of dependencies to boot.

You can implement your code entirely in the .sip file, as well. (See
%MethodCode)  The sip preprocessor will handle all the generation of
type conversion code for you.

James

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde

[prev in list] [next in list] [prev in thread] [next in thread]