Skip navigation.

GNOME Platform Bindings release set

GTK
GTK

Murray Cumming wrote: We now have a GNOME Platform Bindings release set. This means that we cangive some bindings a schedule and rules to work within, and we can endoresthose bindings.Rules:
http://developer.gnome.org/dotplan/bindings/rules.html
Schedule:
http://www.gnome.org/start/2.5/bindings/

Note that those rules do not guarantee 100% API coverage, but they do
guarantee API/ABI stability.

At the moment, it's just gtkmm (C++) and gtk2-perl (Perl):
http://www.gnome.org/start/2.5/bindings/modules.html

Expect others in the GNOME 2.8 schedule. I really think that Python should
be in 2.6 too, and others if they can do it. For 2.6, they have until
December 22nd to give us the list of modules that they want to be put in the
release set. Gtk# say they will do it unofficially and hope to be in 2.8.

If you have questions about the GNOME Platform Bindings release set please
send email to language-bindings@gnome.org. CC release-team@gnome.org if you
want to appeal to a higher power. This might be reorganized a bit in future.

Re: GNOME Platform Bindings release set

First, I agree that bindings shouldn't be included in the release until the API is relatively stable. Programs that have the occasional bug are ok, since bugfixes typically won't obsolete your work. Bindings that have bugs and that are under development are counter-productive. If I write an app in GTK#, and 6 months down the road the thing requires surgery to get it to compile, I'll be pissed. When people install Gnome's stable version, they're expecting something relatively stable...not something that's rapidly changing. Mono/GTK# are a fantastic combination, but let's leave it 'till the bindings are a little more robust.

As for mon, it's not controlled by a company. Ximian endorses it heavily, and started the project, and Microsoft developed the original specifications, but the project remains open source, and completely free.

As for C#, it has been submitted to the ECMA for standardization. It is completely out of Microsoft's control.

I really don't see the problem here. There's no reason not to embrace this fantastic technology other than to maintain a purist attitude (which is counterproductive to say the least). Granted, I'd be a little hesitant about buying into mono 100% at the moment, as I'm still not convinced that Microsoft is just giving this technology away, but there's nothing wrong with C#.