[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ANNOUNCE: RIGS 0.2.1 - Ruby Interface to GNUstep

From: Adam Fedor
Subject: ANNOUNCE: RIGS 0.2.1 - Ruby Interface to GNUstep
Date: Fri, 12 Oct 2001 08:48:17 -0600
User-agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:0.9.4) Gecko/20010915

Noteworthy changes in Version 0.2.1
   * Modified initialization process when Ruby is invoked from
     within an ObjC/GNUstep application.
   * Objective C structures are now handled as CStruct objects in
     Ruby instead of plain Ruby Array. Allow the redefinition of
     method NSRect size and NSRange length without overriding
     those from the native Array class
   * GSTable, GSVbox, GSHbox now imported with the Foundation
     module in Ruby. (GNUstep specific classes)
   * Currency Converter GUI application written in Ruby available
     in the Examples directory

See ChangeLog for more details

RIGS is available at
and soon at

What is RIGS ?

RIGS stands for Ruby Interface for GNUstep. It is a package allowing
integration between Ruby and Objective-C/GNUstep. The main purpose of
RIGS is to allow the use the GNUstep development environment from

One of the most interesting feature of RIGS is that it is 100%
dynamic. It means that RIGS maps Ruby object/methods to GNUstep and
vice/versa entirely on the fly when running the Ruby script. As a
consequence there is no need to generate any kind of wrapping code to
use either existing GNUstep classes or even new ones that you have
developped by yourself. Simply compile your new classes in a shared
library and then do a simple:

require('MyNewClass')       # load your extra ObjC shared library
Rigs.import("MyNewClass")   # dynamically import the class in Ruby

and you are in business! Cool, hey.

RIGS allows you to write optimized classes and components in
Objective-C, and make them available to Ruby developers. Ruby is a
great OO programming language and it is real fun to write GNUstep
applications directly from Ruby.

By the way GNUstep users who don't known Ruby can learn more at And Ruby users that don't know about
GNUstep can go to In both cases, it's
definitely worth a visit.

RIGS is free software and part of the GNU/GNUstep project, freely
available from the Free Software Foundation under the GNU LGPL
license. (Some sample Ruby scripts are under GPL)


CAUTION!! This is alpha software. It is still work in progress
both because the project is just starting and because I'm new to
GNUstep and I'm learning as I go. However you can already play with
it, report problems and contribute new code. (See the Examples and
Testing directories for code samples). For known limitations see the
TODO file.

RIGS is very similar in spirit to JIGS, the remarkable Java to GNUstep
interface written by Nicola Pero. However, unlike JIGS, RIGS doesn't
focus on accessing Ruby classes from Objective C.


RIGS was brought to you by Laurent Julliard
and was built in my spare time when my 3 children are in bed :-))


Laurent Julliard <address@hidden> is on duty!
Helpers welcome

Software Needed to Use RIGS

To use the RIGS, you need:

  * A version of the Objective-C runtime library compiled as a shared
  library (and working with GNUstep).  Please refer to the INSTALL
  file for more information on how to compile and install it.

  * GNUstep make package and base library.

  * A properly installed ruby environment version 1.6.4 or later

Special Thanks

To Avi Bryant (address@hidden> who wrote the very first version of this
version. I took it as a game and then I got trapped! (Thanks Avi...)

To Nicola Pero <address@hidden> for writing JIGS, the brilliant
Java Interface to GNUstep. JIGS has been (and still is) a constant
source of inspiration for RIGS.

To Tom White <address@hidden> for testing RIGS on GNUstep for
Windows and on MAC OS X.

Obtaining RIGS

RIGS is available at

New releases are posted on the GNUstep mailing lists (see as well as ruby mailing

You may always get the latest version of RIGS from the GNUstep CVS -
the module is called 'ruby'. Instructions to checkout a working copy
are available at

Bug Reports

The best way to submit bug reports and fixes is to email them to

reply via email to

[Prev in Thread] Current Thread [Next in Thread]