I don't distribute programs.... I write for my own machines, and for educational examples. But, if I was to do it, I would put your code into it's own module, then tar gzip it up, and you could mail it to them on disks, or deliver it electronically to them. I asked Captain Jack once, about including Tk in Camelbox, but there was some problem. Anyways, you can convert most Tk apps to a Gtk2 app, and you probably should look at ActiveState's Tkx and ActivePerl.
The original allure of Tk on Windows was that ActivePerl included a running Tk.... but no more.....ActiveState got tired of waiting for Tk to modernize, and spun off their own....Tkx.... so why not write in Tkx?..... it's probably better for you on Window's platforms.... they probably have an installer for you app too.
| [reply] |
Thanks for your answer. I will take a look at ActiveState Perl again. I think I decided to use Camelbox in the first place because it comes with Tk and PAR::Packer and I couldn't make Tk work with ActiveState Perl (this might be the case because I sometimes suck at solving problems).
| [reply] |
If you havn't yet googled it, read ActiveState and the old Perl/TkBut you might not get any support from ActiveState for that Tk, and it may be an old version.
It all points to using Gtk2, think long term. It might be easier to convert the Tk app to Gtk2, than it will be to jump thru hoops to keep generic Tk going on Windows :-) Even easier... have clients install Linux....it all works well on linux. :-)
| [reply] |