Kross/KDEBindings Meeting in Berlin : Day 2

So this is the second day of the meeting. Today, we were supposed to speak of the big problem of documentation and examples for bindings, which are truly needed to attract people to use the bindings, but somehow we got absorbed by a coding frenzy, and we only talk about how to organize the kdebindings module (and decide that it would need to be discussed with packagers). So today, I mostly tried to fixed the two annoying crashes that I had with Krita + Kross + QtRuby, and somehow I am unhappy, since I only worked around them, the first one was caused by a nuisance of C++, you can’t know when static objects are going to be deleted, and one of them is deleted too early. Since it happen at exit time, the dirty solution is to not free all memory (it’s not a big deal, but it’s plain ugly). The second issue was caused by a call to the garbage collector of ruby, while an object returned by a ruby function was not anymore referenced, I just removed the call to the garbage collector (clean, isn’t it ?). Then in the afternoon, I spend a little time making sure the build system work as expected, meaning auto-detection of libraries and auto-activation of features, I hope it will make the bindings easier to build in the future.

This entry was posted in Krita, Open Source and tagged , , , . Bookmark the permalink.

One Response to Kross/KDEBindings Meeting in Berlin : Day 2

  1. numerodix says:

    > the big problem of documentation and examples for bindings, which are truly needed to attract people to use the bindingsRoger that. I’ve been meaning to try out the bindings (even if it’s just javascript) for months. But every time I look around it seems to be “too early” as I can’t find any tutorials on it.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>