I'm afraid it's been quite a while since you used Tcl. The namespace support was added about 7 years ago, and Tcl supports several different flavors of OO ranging from C++ like [incr Tcl] to Ruby-esque XOTcl (Exotical) and the delegation-based (not inheritance based) SNIT (Snit Is Not Incr).
The Tk GUI rework started in earnest 3 years ago, largely driven by folks who use Tk for the GUI in commercial applications.
If you were using Tcl/Tk before namespaces, you were probably using it before the better window organizers were added. The grid window manager is much easier to use for complex GUIs than the old pack and place tools were.
The main problem most developers have with Tk GUIs now is that it's so easy to construct a GUI in Tk that they don't give it the thought that they would if the tools were harder to use. It's so easy to hack out a bad GUI that too few folks take the time to hack out a good one.
Like the other small languages, Tcl is always evolving, stealing good ideas from Ruby and Perl just as they incorporate good ideas from other languages. If you last looked at Tcl/Tk more than 3 years ago, you haven't looked at Tcl.
Slashdot Mirror
The Tk GUI rework started in earnest 3 years ago, largely driven by folks who use Tk for the GUI in commercial applications.
If you were using Tcl/Tk before namespaces, you were probably using it before the better window organizers were added. The grid window manager is much easier to use for complex GUIs than the old pack and place tools were.
The main problem most developers have with Tk GUIs now is that it's so easy to construct a GUI in Tk that they don't give it the thought that they would if the tools were harder to use. It's so easy to hack out a bad GUI that too few folks take the time to hack out a good one.
Like the other small languages, Tcl is always evolving, stealing good ideas from Ruby and Perl just as they incorporate good ideas from other languages. If you last looked at Tcl/Tk more than 3 years ago, you haven't looked at Tcl.