The reason I was looking at writting up my own bindings is I've been working on designing and developing yet another interpreted language. It started out as a personal educational project, but then I started getting some feedback and have been making improvements based on what some of my users were wanting. And everytime I start adding something, I discover some additional needed constructs to through in there.

Since I've been looking at picking up an N800 (since they've gotten so cheap lately), and since there are a few apps that I'd like that don't exist yet for it, I figured what better way to exercise and strenghen my interpreter than to set up some gui bindings for it and see how far I can stretch the language. Plus, I'm not that big of a fan of Python (mostly because of the requirement to mark blocks of code by indententation level).

In case anyone is interested, the language I've been designing is called 2e (as in two E's, which stands for "expression evaluator"). (http://lang2e.sourceforge.net) The language is a weak-typed, dynamic typed imperative language with support for dynamic typed & untyped arrays, functions are call-by-reference, and supports first class functions and dynamicly loaded function libraries. The external function library support is what I want to excercise by writing up GTK/Hildon bindings.

I've gotten enought bindings defined to get through most of the standard GTK tutorial, but then started writting a code generator to try to automate as much of the process as possible. But looking through the GTK reference, it looks like there are several objects that would only be used rarely, so I was hoping to get a "readers digest" version that had maybe the top 50 or so most needed functions.

Another option I may consider is to write a code analyser that pulls out which functions are used in most of the available source packages on maemo.org.