Alex Fenton <alex / deleteme.pressure.to> wrote:
> Doing the survey prompted me to try out Ruby's stdlib Tk on OS X - just 
> running a couple of the samples. I don't know, is what comes with Ruby 
> 'classic' by default?
> 
> It's another reason why I think Ruby-Tk would be best hived off out of 
> the standard library to a separate project. If it takes installing some 
> extra packages after installing Ruby to make Tk look as good as 
> possible, then why wouldn't a user just install some other GUI package 
> that's at the end of a 'gem install xxx' command.


Hi Alex,

Thanks for the reply.  I don't disagree at all, but I did want to 
clarify one thing related to the above.

Ruby/Tk already comes with both the 'classic' and the 'themed' widget 
sets out of the box, with nothing at all extra to install.  The catch, 
and it's no small one, is that the two widget sets have slightly 
different API's in places.  

Because of that, if you ask for a button using the same Ruby/Tk code as 
you were using before, you still get the old button, whereas you have to 
use a different call to get the themed variant ... it amounts to 
replacing 'TkButton.new' with 'Tk::Tile::Button.new'.  So if you don't 
know to update the code (and how are people supposed to find that out), 
your GUI still looks pretty shitty.

Thanks again
Mark