Re: Tk causes problems with file paths containing non-Latin-1 chars

I have a module that makes exactly same approach at using GUI!
It was developed at my work and I am using in a whole bunch in my utilities - I just specify predefined array, which declares parameters, and - all is ready!

If then my script is fed by --g, it shows GUI for entering any of arguments, with handy explanations on the left, and this is really convenient, because I have supported several types of arguments: boolean becomes checkbox on GUI, choise is either dropdown box or just list to select a vaule, also I have a file/directory selection (either input or output) and just string for any other parameter

Also, it supports drag-n-drop of files and directories too, so you could drop a file from file manager into the input box.

I can show more details, if there are any interest.

Tk module uses is Tcl::Tk, which is really better than perl/Tk, due to many reasons - I switched long ago from per/Tk and never looked back.

Comment on Re: Tk causes problems with file paths containing non-Latin-1 chars Download Code

Replies are listed 'Best First'.
Re^2: Tk causes problems with file paths containing non-Latin-1 chars by ron7 (Beadle) on May 03, 2011 at 23:00 UTC
Thanks for the suggestion, but I'm constrained to whatever ActiveState supports as my users are mostly non-technical windows weenies who need exe files they can double-click to launch an app. So I use AS's perl app builder and generate binaries for Linux, win32, and OS-X which works fine except for the extended char in path problem, now fixed for all but win32, which is 95% of my users!! grrr...	[reply]
Re^3: Tk causes problems with file paths containing non-Latin-1 chars by vkon (Curate) on May 04, 2011 at 06:19 UTC
Tcl::Tk is pure-perl, 4 pm files, no dependencies other than Tcl CPAN module, so it should be no problem in packaging it, so using even easier than Tkx, because you will have perl/Tk syntax for your programs.	[reply]