Ruby-GNOME2 moves to GitHub

Ruby
1

Hi!

The Ruby-GNOME2 team has been hard at work the last few months to
bring you updates in a wide range of areas.

  • Ruby 1.9

Ruby-GNOME2 now compiles and runs without warnings or errors against
both Ruby 1.8 and Ruby 1.9.1 ABIs. That means that you can use it
with Ruby 1.8.7, 1.9.1, 1.9.2, and 1.9.3.

Support for String encodings in the 1.9 series has also been improved.

Initial investigations into improving concurrency in Ruby 1.9 has also
been made, but will require a lot of work to get done.

  • Memory management

A thorough audit of memory allocations has been made and many
potential memory leaks have been plugged.

Garbage collection protection has also been improved, fixing problems
that could previously occur in seemingly random ways.

  • Ease of build

The build system has been vastly improved, supporting gem building and
binary gems for Windows.

  • Ease of documentation

A new documentation system based on YARD has been implemented and is
currently being applied. This will improve both the documentation
quality and its accessibility.

  • Ease of definition of new interfaces

The process of linking C functions to Ruby methods has been
simplified. This makes both documentation and interfaces easier to
write and keep in sync.

  • Bug removal

As a result of other changes, a large portion of the source code has
been thoroughly reviewed and updated, with quite a few bugs being
removed.

  • Gtk+ 3 support

Support for Gtk+ 3 is currently being implemented. This is a sizable
task and will require a lot of work. Gtk+ 3 is, however, the future
and the Gtk+ 2 is now in maintenance mode.

  • GitHub hosting

Ruby-GNOME2 is now hosted on GitHub and the Git repository is the main
repository. The Subversion repository has been closed.

The Ruby-GNOME2 repository can thus now be found at

  • GObject-introspection

Initial investigations into using GObject-introspection have begun.
This is another sizable task that will require a lot of work, but
promises huge winnings.

  • Contributing

We are quite pleased with the progress that we’re making, but we could
really use a few extra hands. The areas that we particularly want to
improve is documentation, Ruby 1.9, and Gtk+ 3. So fork us on GitHub
and begin submitting your pull requests!

Thanks,

2

Kouhei S. wrote in post #1032509:

[lot of awesome news]

  • GitHub hosting

Ruby-GNOME2 is now hosted on GitHub and the Git repository is the main
repository. The Subversion repository has been closed.

The Ruby-GNOME2 repository can thus now be found at

GitHub - ruby-gnome/ruby-gnome: A set of bindings for the GNOME libraries to use from Ruby.

WOW, great stuff, including the move to GitHub!

–
Luis L.

3

Kouhei S. escreveu isso a:

  • Gtk+ 3 support

Support for Gtk+ 3 is currently being implemented. This is a sizable
task and will require a lot of work. Gtk+ 3 is, however, the future
and the Gtk+ 2 is now in maintenance mode.
[…]

  • GObject-introspection

Initial investigations into using GObject-introspection have begun.
This is another sizable task that will require a lot of work, but
promises huge winnings.

It looks like other bindings (e.g. pygtk) were deprecated in favor of
using a solution based on GObject-introspectioni, what would that mean
for ruby-gnome2? Do you guys intend to maintain both a hand-made Gtk+ 3
port and GObject-introspection bindings?

4

Congrats!
A little OT, is possible to make Gedit Plugins?

Luigi

5

On Mon, Nov 21, 2011 at 18:46, Antonio Terceiro
[email protected] wrote:

Kouhei S. escreveu isso aí:

  • GObject-introspection

Initial investigations into using GObject-introspection have begun.
This is another sizable task that will require a lot of work, but
promises huge winnings.

It looks like other bindings (e.g. pygtk) were deprecated in favor of
using a solution based on GObject-introspectioni, what would that mean
for ruby-gnome2? Do you guys intend to maintain both a hand-made Gtk+ 3
port and GObject-introspection bindings?

There will probably be a bit of both in the end. To make the APIs
more Ruby-friendly, you’ll always have to provide some purpose-written
wrappers.