> >> ...that "The Tk Way" equals "Nothing works out
> >> of the box"?)
>
> mdiam said:
> > ... the **Ruby/Tk** is difficult to make working
> > only because Tk is not part of Ruby.
>
> It isn't? Well. Actually, if it was shipped as a
> gem we could just do "gem update tk" and it'd work
> with the newest Tk, wouldn't it?

I agree that a "gem upgrade tk" would be nice, but
I'm not sure it's feasable while Tk is not part
of Ruby?
-- Maurice