[Marble-devel] Python bindings committed

[Torsten Rahn]

Hi Simon,

your bindings would be a lot more appealing if you'd provide a description

a) what one needs to work with them (in terms of packages)
b) how to use them -- Here some basic instructions would help a lot ... At 
least I was not able to use them with my limited python knowledge ....

Thanks,
Torsten

> Oh, I forgot something :-)
>
> Could you maybe add a few sentences about how to use the MarbleWidget with
> the python bindings on:
>
> http://techbase.kde.org/Development/Tutorials#Using_MarbleWidget_.28Marble.
>29
>
> I've seen that you had committed an example already but nevertheless a few
> additional sentences on the wiki and maybe a hint at all that Python
> bindings do exist wouldn't hurt, but rather increase the likelyhood that
> your work gets noticed by potential users of the bindings.
>
> Regards,
> Torsten
>
> On Sunday 19 October 2008 13:18:19 Simon Edwards wrote:
> > Hello,
> >
> > I've committed the Python bindings. They are mostly complete. I'm
> > missing a couple of geodata classes which will require some hand written
> > stuff, but that can come later. I've also checked in a very small python
> > program which just displays a marble widget. It works(!). Sometime
> > around the 4.2 betas and RCs I'll update the bindings from the header
> > files, although I might do some of the manual work before that.
> >
> > I've added the MARBLE_EXPORT thingy to ClipPainter to make it visible in
> > the library.
> >
> > Some other comments about the headers:
> >
> > * src/lib/geodata/data/*.h is installed, but the other
> > src/lib/geodata/scene and parser are not.
> >
> > * There are some surprising uses of qreal _references_ instead of a just
> > qreals which are only used for passing in parameters.
> >
> > If for some reason the API changes and the bindings break and break the
> > build, you can comment out the python directory in the CMakeLists.txt
> > file if needed.
> >
> > cheers,