ANN: PyKDE now does KDE plugins

[John J. Lee]

Jim Bublitz <jbublitzno at spamnwinternet.com> writes:
[...]
> required. This is the first in what's planned to be a number of
> extensions for PyKDE that allow plugins and related objects to
> be created entirely in Python; David Boddie is nearing release
> of modules for authoring KParts for export (PyKDE already
> imports KParts), KDE Control Center modules, and IOSlaves.
> 
> Future plans include allowing QWidget subclasses created in
> Python to be imported into Qt Designer with complete
> functionality, and possibly Python scripting and plugins for KDE
> apps like KOffice and Kontact. The underlying mechanisms and
> code are similar in all cases.
[...]

Wow, sounds like impressive stuff.  How does it work?  Is there a
standard .so proxy that can be used by all Python plugins?  What sort
of memory footprint do these plugins have?


> In some cases, specific .so libs will still be required (depends
> on the plugin loader), but the Python modules will include
> autogeneration of the necessary C++ code, along with installers
> to simplify the task of making the plugins available.

What makes the difference between all-Python and needing a bit of C++
here?


John