in reply to Re^2: Tkx combobox error on quit
in thread Tkx combobox error on quit

Use pure Tk, if Tkx dosn't have DONT_WAIT.
I'm not really a human, but I play one on earth Remember How Lucky You Are

Replies are listed 'Best First'.
Re^4: Tkx combobox error on quit
by vkon (Curate) on Sep 23, 2008 at 14:56 UTC
    Tkx is closer to "pure" Tk (meaning Tcl/Tk) than perl/Tk, so there is much more chances to write better quality software in Tkx than in perl/Tk.

    Perl/Tk is outdated by construction.

[reply]
      Perl/Tk is outdated by construction

      I agree. I recommend Perl/Gtk2 to people who are looking for something with good fundamental design. But Tk will be around for a long time, because of it's userbase and ease-of-use for simple things.

      I'm not really a human, but I play one on earth Remember How Lucky You Are
[reply]
        its okay to prefer perl/Gtk2 over perl/Tk or Tkx or perl/TclTk.
        I aware of benefits of Gtk2 over Tk (better unicode, more fundamental design indeed)

        However I do prefer Perl/TclTk for the following simple reasons, from the top of my head:

        • Tk-8.5 looks good on linux (8.4 was much worse due to fonts rendering, although this never was a problem on windows)
        • programming Gtk2 seems much more noisy to me. Tcl/Tk GUI code is usually very short and thus more understandable.
        • Tcl/Tk is very lightweight. It is essential when creating PAR distros for Windows. 3MBytes of extra weight and no dependencies on installed GUI library with a huge widget set.
          Gtk2, on the contrary, requires large directory, it isn't always easy to manage it on windows (DLL with same name on PATH is usually a problem)

        Best regards,
        Vadim.

[reply]

In Section Seekers of Perl Wisdom