Conrad Schneiker <schneik / us.ibm.com> wrote:
> > Michael Lam writes:
> > # I have some experiences with SWIG (and know how easy it is to use). Can the
> > # author of SWIG/Ruby please stand up, and let us know how possible wxRuby is if
> > # we use SWIG, just like the wxPython guys do?
> > 
> > Why not ask him directly? His given mail address ends in .jp, which may
> > mean that he might not follow the English mail list or comp.lang.ruby. So
> > I have cc:'d him on this post (which is probably a good idea for questions
> > addressed to anyone who is not racking up frequent poster points here).
> 
> Well, no response so far, and no bounced mail. Might be on vacation.

I'm sorry I couldn't respond quickly.  Yes, I have been away from
home for two weeks.  But not on vacation.  I wish I were...

Basically wxRuby can be developed with SWIG as wxPython was.  I
took a quick look at wxPython source code.  wxPython has many
SWIG interface files (*.i).  I found no small proportion of the
interface files have Python native API calls.  That means they
are not fully portable to SWIG/Ruby.  You have to write the Ruby
counterpart of the native API calls.

> And does anyone else have any experience with SWIG/Ruby for Ruby 1.6+?

SWIG should operate with Ruby 1.6.  If not, it's a bug.


Masaki Fukushima