User login

Navigation

Contribute

Interested in contributing to FootNotes? Click here to submit news stories to us or visit this site for more information about available opportunities.

GNOME Support

Friends of GNOME

Now's a good time to say thanks for the best desktop environment on the planet by becoming a Friend of GNOME or by upping your current Friends level. Contribute by joining the Friends of GNOME program. All contributions are tax-deductible in the U.S. Thanks to our generous Friends

Links of Interest

Syndicate

GNOME Platform Bindings release set

Submitted by stro on Tue, 2003-12-09 13:29. 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

Submitted by Anonymous George on Wed, 2003-12-10 07:31.

ECMA is as far as i know not a stardatisation organisation like ISO or ANSI or W3C, it just get's input and declares it as standard; that means i could do the same job (anyway but i believe that no one will respect my standards).

on the other side C# is only the language specs and mono is the .NET equavalent. so they don't have much in common.

ok you're right that mono is mostly opensource but not fully complaining to LGPL, GPL or BSD like licences. so wasn't the main idea (beginning from the roots) to build a real OPENSOURCE desktop environment?

but the main idea behind mono is not just that it will have std. bindings and modules which are language independent. BUT

KEEP IN MIND that ximian - which is the main developer of the mono platform - is part of Novell like SuSe. who's trying to save it's own ass. it's buying companies with fresh blood to keep it-self alive. that reminds me to an episode of futurama where the prof. says "it's good to have Amie in visible distance in case he needs freshblood."

i got a little bit distracted, sorry. anyway the main positive of the mono project will be the mix of write-once-run-everywhere and write-once-use-with-all-languages. and that's still something that is controlled from MS. and the company who supports the main development to put it on other platforms in this case Novell. that again means that we would be hardly dependent from 2 big companies. isn't one of the main ideas of opensource being independent? or does it only mean for you free of charge?

so going from the worst case if things should go wrong the ability to write-once-run-everywhere will sleeping with the fishes... and worser we will have to so a split from the novell's mono projects, like this happend a few months ago with XFree.

» parent