Language Bindings for the C++ API

Blog post by jalopeura on Wed, 2011-04-27 08:06

My project will expose the Haiku API to scripting languages. During GSoC, I will focus on enabling the creation of GUI apps; this will include large parts of the Interface Kit and some essential classes from the Application Kit. I will target Perl and Python as the scripting languages.

(After GSoC, I would like to support other languages as well, and increase the number of classes available from scripting languages.)

A timeline is available by following this link.

During the bonding period, I will be looking at the Python API, with a view to developing a generator to create the code for these extensions from an abstraction language, as an alternative to using SWIG. (I will not make a final decision on whether to use SWIG until I have determined whether it is feasible to use a custom-built generator within the GSoC time frame.)

Comments

Re: GSoC Milestone Report: Acceptance

There is Lisp, Lua and such also... though I am biased towards Lisp, MurgaLua was/is pretty popular for writing little programs on DSL and Puppylinux... it was basically Lua + FLTK jammed together.

Re: GSoC Milestone Report: Acceptance

Don't forget to give us access to ACPI readouts, i need scripting access to things like battery level and wifi connectivity for an app I'm working on :) cheers

Re: Language Bindings for the C++ API

Thank you! This is awesome news for people like me who don't like C/C++!

Re: Language Bindings for the C++ API

When do you start???