Older blog entries for jluke (starting at number 4)

So i wasted yesterday trying to debug a binding that should be working but just doesn't. The C# code works, the C code works. One function just always returns false. I wish I knew how to use gdb better. Same thing with the vte-binding, it breaks in the managed/unmanaged boundary and I haven't yet figured out how to debug that very well.

Perl is so unreadable if you did not write it. Even when written by very smart people.

Source Editors

It's a tough choice to make, but we are fortunate to have 2 rather good choices with support from both groups (SD and gtksourceview). One thing is that the SourceEditor implementation is different enough from the SD TextEditor that adding the language bindings from SharpDevelop you have to port it instead of just copying it over and it works. Not terribly difficult but an area that being compatible would be nice.

update I fixed vte with two lines of metadata, which makes me feel really stupid. cvs up and try out the sample in gtk-sharp/samples/vte-test.exe

I just finished an initial port of the SharpDevelop Java support to MonoDevelop. So now those who like Java can use MonoDevelop to do simple projects. I have only tested the included projects, so beware on anything else. I did this mostly so I can get an idea of what kind of work it takes to add an additional language. Of course, it turns out to be relatively easy, at least as far as syntax highlighting and project support goes (parsing and code completion is more difficult). Perhaps I'll add a small doc to explain breifly what is required.

Perhaps someone will come along and add a way to directly use mono and IKVM instead of a java runtime and compiler which would be nice, as well as a Java/Gtk# project. (Hint: it probably won't be me)

Edd has posted another well-written and thought out blog over on planet gnome. I just wanted to second what he said and add some thoughts about documentation.

Some of Gtk is documented very well, but you quickly go down hill if you need explanations in a language other than C, or one of the other libraries. Although we have the advantage of looking through others source, documentation is often much easier for people outside the regular group to find what they need.

I think we need to have a way for the api docs on http://developer.gnome.org/ to have examples in multiple (programming) languages and be filtered for the users language of choice. This of course means we need to include bindings for other languages in the gnome releases as officially supported languages.

Hopefully we can convince some of the GNOME supporting companies to employ more resources to documentation, even if it's just some interns or part-time employees. It can be overwhelming for volunteers (I should know because I wrote/ported a lot of the Gtk# docs).

Last, I wanted to mention that this page has been very helpful in learning some of the things about GNOME/GTK that I didn't find anywhere else. I only wish I would have read it _before_ we began porting SharpDevelop to MonoDevelop.

Since the integrated debugger in MonoDevelop is rather dependancy heavy we decided to make it conditionally compile (we will probably do the same for the integrated monodoc). Todd did most of the work and I just finished the Makefiles. So if you are living with a 2.4 kernel w/o NPTL you can compile MonoDevelop again. But the rest of you still get debugging goodness.

Also, today I had to write a small hack for RSS.NET to parse the PubDates for this feed so you can read Paolo's excellent posts on Monologue. Seems like neither mono or .NET support dates in this format:

Fri, 19 Mar 2004 15:13:02 -0700

but it does support:

Fri, 19 Mar 2004 15:13:02 GMT

which is especially strange because I think they are both part of RFC822.

Oh so it works. Work continues at a feverish pace on MonoDevelop. Some better cooperation with SharpDevelop may begin to happen. I guess we are taken more seriously now. Please file more bugs if you are using MonoDevelop.