[PyQt] PyKDE4 Update

[Simon Edwards]

Jim Bublitz wrote:
> The first is how large should PyKDE be? At some point I'd want to start 
> splitting stuff off into a second package, and all 3 you mentioned would be 
> good candidates for that. They're not really central to kdelibs for what I 
> see as the average user.

I was think about that the other day when I realised that Kate and its 
.h file isn't even in kdelibs, but kdesdk or something. We could put 
everything in PyKDE4 and create some extra configure time flags for 
turning certain dependencies on or off. e.g. "just give me bindings for 
everything in kdelibs and that's all" or "give me the lot"). A second 
package PyKDE4EverythingElse has its advantages too. For a start, we 
might get more consistent and clearer packaging. With less of this 
"Dammit! XYZ compile their pykde4 package with API ABC turned off! but 
everyone else has it compiled in!". PyKDE4 would then depend on kdelibs 
and maybe kdepimlibs, like kdebase does. And PyKDE4EverythingElse could 
have much large dependencies like, well, everything else.

Another API which I would like to have bindings for is Marble. I was a 
bit surprised to find that it isn't part of kdeui, but kdeedu module.

> Learning 
> threading or symantic desktops is not high on my list of priorities, but I'll 
> get to it eventually (a year or two).

Semantic desktop API is probably useful, but the threading API sounds 
like a big can of worms for Python programs running on CPython.

> Someone can speed that up by 
> volunteering to debug bindings for those packages AND producing test 
> code/examples or (at best) a tutorial. Docs I can get for free from the h 
> files.

True, if someone is interested in an API and can help out, then it can 
be given high priority.

cheers,

-- 
Simon Edwards             | KDE-NL, Guidance tools, Guarddog Firewall
simon at simonzone.com       | http://www.simonzone.com/software/
Nijmegen, The Netherlands | "ZooTV? You made the right choice."