in reply to Re: Threads-w-Perl/Gtk2 demo
in thread Threads-w-Perl/Gtk2 demo
I meant that solely in the context of Tk programmers who want to convert to Gtk2, and run into problems with a single button being used in different contexts, like doing different things depending on what the button text or state is. It just shows the extra depth of the Gtk2 toolkit, a depth beyond what Tk allows.
Is Tk easier than Perl/gtk?
Oh yeah, way easier. For example, Gtk2 is hard to set individual widget colors. It can be done, but Tk is way easier.
`cpan Tk` installed without a single hitch in 32-win strawberry perl whereas perl/gtk required hours of teeth gnashing. wxperl is easy to install on windows too.
Yes you are right. I found Camelbox: A build of Gtk2-Perl for Windows easy to use for my limited Window's testing, but I have to admit Strawberry is probably a better way to go. Camelbox makes it difficult to add anything to it. WxPerl is usually based on Gtk2, but it is a C++ wrapper aroung the plain C gtk+. I would probably have to say wxperl is probably better if you like the OO style of C++ programming. Me, I like the C style, but don't let my "old dog" ways stop you from wxperl, its just that I'm a functional style programmer. Also, on linux, putting in Gtk2 is easy as pie, and I hate seeing Gtk get a bad wrap just because of a crappy Windows compiler environment.
do you prefer gtk over wxperl and tk?
I prefer Tk as number 1, but it has many drawbacks for more advanced work. Gtk2 is way better with threads, as is WxPerl, since it is built on the Gtk2 libraries. Also, many new libraries are emerging like gstreamer, libsoup, and you name your own. Gtk2 and Wxperl are hopping right on those, whearas Tk is left behind. Especially for anything threaded, you would want to use Gtk2 or WxPerl.
But that said, Tk still fulfill the needs of probably 90% of the problems out there, but it is wise to learn either Wx or Gtk2 to keep up with the new stuff coming out.
|
|---|