Re: [wxperl-users] porting a perl/tk application to perl/wx

[John R. <jr...@ce...>]

On Mar 5, 2007, at 2:48 PM, Bob Hunter wrote:

>
> I'm so close to scream like an awk to this python...
>
> ...and stick to Tk. Why is that Perl/Wx must be so
> cumbersome? Perl/Tk is so easy to manage by hand, by
> comparison. After all, we are talking about Perl/Wx,
> which everyone assumed it to have the same coding ease
> of Perl/Tk. Why is that Perl/Wx is so cumbersome? Who
> cares about all those details? Why can't Perl/Wx be as
> easy as Perl/Tk? Can't you make an effort to hide the
> complexity, and deliver an API that is similar,
> whether not identical to Perl/Tk?
>
> Bob

I think that you misunderstand both wxWidgets and wxPerl.

wxPerl is a wrapper around (most of) wxWidgets. It is not  
particularly perlish, and it is most definitely not like Perl/Tk,  
because wxWidgets isn't like Tk.

wxWidgets in turn wraps various platform GUI frameworks -- Carbon or  
Cocoa for OSX, GTK (and not as well developed, Motif) for X11, Win32,  
Wince, PalmOS, and others. It also provides a common API to some of  
the underlying OS services, like sockets, and fills in holes in some  
areas like regular expressions. It's a C++ library, for which  
wrappers in other languages are available, including wxPerl and  
wxPython.

wxWidgets is emphatically *not* intended to do what Tk does: Provide  
a quick-and-dirty graphical front end to quick-and-dirty "scripts".  
It *is* a full-featured framework for developing full-featured  
applications.

Only you can decide which is the more appropriate tool for your use.

Regards,
John Ralls