"Dave Thomas" <Dave / PragmaticProgrammer.com> wrote

> "Conrad Schneiker" <schneiker / jump.net> writes:
>
> > > And... I'd like to discuss deployment issues too. If we want to
> > > make this _the_ Ruby GUI,
> >
> > Hmm. How about calling it the
> > next|2nd|modern|mainstream|preferred|recommended Ruby GUI. You don't
> > mean to drop Ruby/Tk do you?
>
> By "the" I mean the GUI of choice. If we make it ubiquitous, easy to
> use, and full of useful features, then I'm assuming that developers
> will write to it in preference to other packages.

I think that's perfectly fine (actually I think that's *great*)--but that
wasn't quite what I was asking.

To put it more concretely, would Ruby/TK still be retained in the
(principal) InstallShield distribution of Ruby? Would the Tk module still be
included in the (principal) Ruby tarball? And would the Tk module be updated
when Tk8.4 exits beta? With a good alternative, I personally wouldn't miss
it at all, but (some unknown numbers of) others who wrote (say) Ruby/Tk
utility programs in the last few months or years might.

Conrad