[Marble-devel] Python bindings for the Marble widget and friends

[Torsten Rahn]

Hi Simon,

On Thursday 16 October 2008 16:19:17 Simon Edwards wrote:
> The soft feature freeze is almost here but there is one thing that I've
> wanted to have for a while now and which I want to get in for KDE 4.2.
> Python bindings for the marble widget so that I can use it from my
> Python code.

Wow, that's incredible great news :-)

> I've got the bindings mostly done, and I would like to check they in
> directly to kdeedu (in a marble/src/bindings/python directory). 

Would be fine with me. Is there anything for us to do to make sure that you get 
aware of any future API changes? 
We are trying to get the API more and more stable but we are still at a point 
where we can't fully ensure that the API doesn't change from 0.x to 0.x+1 
releases (however we ensure that it stays the same for 0.x.y to 0.x.y+1 ;-)

> This
> would introduce a an optional Python (PyKDE4/kdebindings module)
> dependency for marble and the kdeedu module. Has anyone got any
> comments, advice or even objections to the python support being kept in
> with kdeedu?

What size do the sources have? I'm all for it (as I consider it convenient if 
the bindings stay in the same module). But of course you'd need to ask 
Anne-Marie and probably also Allen Winter.

> Some technical comments. The ClipPainter class needs to be exported
> otherwise I can't bind to it or the GeoPainter class. 

Be aware that ClipPainter is not meant to be part of the public API (that's 
what GeoPainter is for).

> I also noticed
> that a bunch of header files are installed into /usr/include etc but
> contain non-exported classes. 

Patrick, Inge: could you look into that? :)

> Also some methods in classes specify
> methods without implementations. Are you people interested in more
> details about where the headers could be improved? 

Yes, very much so. We're always interested in suggestions and details :-)