As far as I know perl/Tk will be updated soon to support Unicode in perl-5.8.x
But this is entirely different approach.
Normally you do not need Tcl::Tk when you are satisfied with perlTk, but here are cases when I use it and advice it to use for others:
- sometimes Perl somes without perl/Tk (Linux, FreeBSD and probably other distribution do not have it unless you managed to build perlTk) and compiling perlTk is much more consuming task than Tcl::Tk, because usually Tcl/Tk already exist in system and Tcl::Tk as a glue is really lightweight
Being lightweight, it is much easier to port it to another OS, and, as a bright example, currently Tcl::Tk is the only way to get GUI for perl-5.8.x on WinCE, yet the only way to get Unicode-aware GUI for perl-x.x.x on WinCE.
(OT: FreeBSD has rather old Perl and rather new Tcl/Tk after installing of OS. Why?)
- You need some feature that exists in Tcl/Tk but not available in perlTk. Mostly these are Unicode and large set of widgets available in Tcl/Tk.
- Not only widgets, but some parts of ready-to-use Tcl/Tk code could be used from Perl, as long as perl has full access to all widgets created in Tcl/Tk.
(I use this approach quite often)
- Elder perls could have Unicode-enabled GUI this way.
(I'm still using perl-5.6.1 and really will migrate to perl-5.8.1 soon, but until that I have ability to create Unicode-aware GUI)
Also, Tcl/Tk is updated more frequently than perlTk do.
Courage, the Cowardly Dog