in reply to Re: cross platform gui's
in thread cross platform gui's

... there's an ActiveState PPM for Tk.

You just install Tk and you have a working GUI toolkit. Wx and Gtk are both thin wrappers over external libraries, so you'll need to install either wxWindows or Gtk to make them work.

Why is that important? All the Tk author does is bundle the required Tk files ... you can always build a statically linked Wx (or probably Gtk for that matter).

wxPerl binaries are readily available for perl 5.6 and up, in both unicode and non-unicode flavors. In order to get perlTk with unicode support you need at least perl 5.7.

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re: Re: Re: cross platform gui's
by batkins (Chaplain) on Oct 19, 2003 at 13:06 UTC
    Because Nick merged the Tcl/Tk code into Perl/Tk very well. There's a lot of Perl support code around the Tk core to make the Perl interface nicer. For instance, the Tk callback system is entirely customized for Perl and the object-orientedness of Perl/Tk is completely absent from Tcl/Tk. So instead of having to find an appropriate version of the library your toolkit needs, it's already been integrated into Perl/Tk. Something like Wx is still very C++-ish, which is fine if that's what you want. But I think that by including a particular version of Tk in Perl/Tk and then making a heavy Perl wrapper around that, the code becomes more usable and the install a little simpler.
    The computer can't tell you the emotional story. It can give you the exact mathematical design, but what's missing is the eyebrows. - Frank Zappa
[reply]

In Section Seekers of Perl Wisdom