From: Handy Gandy <handigandy-es@...>
Date: 2010-09-04T03:10:10+09:00
Subject: Tk and Ruby or alternatives ( Re: GUI for commandline programs )

On Fri, 03 Sep 2010 04:20:18 -0500, Brian Candler wrote:

> I should add, that will handle your case (1) and (2) happily, but not
> (3).
> 
> The granddaddy of all these is Tk. I think it should be OK if you want
> to draw some stuff, run the main loop while you wait for user feedback,
> then break out of the main loop to carry on doing normal stuff. I don't
> think you're constrained to a single "main loop".

I have never used Tk, though I have encountered it often. It was actually 
Tk that I ws thinking of when I wrote the post originally, but  I'm under 
the impression that there are several major shortcomings with Tk ( people 
with more practical experience of Tk please feel free to correct my 
impressions ).

Tk itself is falling into disfavor, so it may not be viable for much 
longer.

The Ruby bindings for TK are crude and iffy.

The documentation for the Ruby bindings of Tk is very poor.

The Ruby bindings for TK are not very "Ruby-like".