in reply to Re^3: Why Tkx? And will Tk endure?
in thread Why Tkx? And will Tk endure?

but Perl/Tk development is very much active.

s/very much/just barely/i

Does Tkx support threading? If so that may one of the reasons.

There is really only one reason, Tk.pm has been stalled for at least 8 years. With Tkx, you always have the latest widgets your Tcl/Tk install has to offer, and none have to be ported over to Perl/Tk (which doesn't happen often, happens slowly, and is always filled with bugs).

Replies are listed 'Best First'.
Re^5: Why Tkx? And will Tk endure?
by aplonis (Pilgrim) on Apr 20, 2010 at 14:17 UTC

    I read elsewhere that the author of Tk died in 2006 and on account of the project being so very large nobody wanted to take it on. Hence the fresh beginning with Tkx.

    So now I am wondering if it be too much of a stretch to suppose that with Tkx being the new best thing I could buy a book on TCL/Tk from Amazon, (this one, for instance) and armed only with that, I could carry on just as well as with the old Perl/Tk ... that I'd have nearly as many widgets (Balloon, etc) as before?

    It's not an idle question as I have a PM of my own to re-write, in such case. I never released it to CPAN after being totally unable to grok the CPANTS complaints appearing in my email from the one module I did release. But my very own Tk::EasyGUI.pm will need updating into a Tkx-ish variant. Trying to decide how much bother that is going to be.

    Or should I just bite the bullet and start anew with something else? If so, recommendations? What about wxPerl? Any others?