I have a large Perl/Tk application that
I've been working on for almost 10 years
and continue to enjoy fiddling with:
http://www.suecenter.org
I recently noticed that ActiveState Perl 5.10.1.1007
does not include Tk in the distribution and that
it is not available via ppm either. Rather Tkx
is recommended. Is this all due to Nick's passing
or has Perl/Tk simply 'run its course' and something
better has taken its place?
I can certainly continue using the existing Perl
and Tk that I have but do wonder about directions
for the future.
How difficult will it be to transform a Perl/Tk
application into using Tkx with the different
syntax of widget creation, etc? Is it worth the
trouble?
I've never used the PerlDev Kit
but it looks like it is time for me to do that!
I've been using perl2exe (to build .exe files)
and Advanced Installer (for making the installation)
but the Dev Kit has PerlApp and PerlMSI as alternatives.
Thank you all at ActiveState for your help.
Jon
On May 31, 2010, at 12:00 PM, perl-win32-users-requ...@listserv.activestate.com
wrote:
> Date: Mon, 31 May 2010 09:24:32 -0700
> From: "Jan Dubois" <j...@activestate.com>
> Subject: RE: Tkx vs. Tcl Dev Kit
> To: "'Kanhaiya'" <kpra...@aptaracorp.com>,
> <perl-win32-users@listserv.ActiveState.com>
> Message-ID: <02bb01cb00dd$c0e81a00$42b84e...@activestate.com>
> Content-Type: text/plain; charset="Windows-1252"
>
> Kanhaiya wrote:
>> Whic one is better?for GUI based perl application?
>> ?
>> Perl Tkx
>> OR
>> ActiveTcl with Tcl Dev Kit
>> ?
>> I'm confused and not finding any solution.
>
> I think you are confused about how Tkx actually works:
>
> Tkx is a Perl interface to Tcl/Tk using the Tcl.pm module to access
> a Tcl interpreter.
>
> ActivePerl contains a packaged Tcl interpreter and a set of common
> widgets all bundled with the Tkx module, so this is all you need to
> create Tkx applications with Perl; you don't need ActiveTcl for it.
>
> If you want to install additional Tk widgets, then you can install
> ActiveTcl *in addition* to ActivePerl and configure Tkx to use the
> local Tcl installation instead of the one bundled with ActivePerl.
>
> If you want to wrap a Tkx application into a standalone executable,
> then you may want to use PerlApp from the *Perl* Dev Kit.
>
> Cheers,
> -Jan
_______________________________________________
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
