"I used to churn code based on Tk, and this code was a real spaghetti, gui stuff mixed with actions mixed with logic ... horrible"... !!
Thanks Eyck and all the other guys for your feedback. I just finished my first effort with Perl/Tk and I ended up with 600 lines that look just as you describe above, even though I think I understand the event handler concept... I just couldn't separate stuff like freezing/unfreezing buttons, from stuff to fire up and monitor the background process (via 'After' callback), from stuff to load and validate parameter files, from error handling (very important that absolutely any problem must produce coherent output), from stuff to cleanup zombies on process cancellation... horrible. I got Perl/Tk to do everything I wanted, but it is unmaintainable code. So big plus and big minus. Anything out there to force some function separation into Perl/Tk ?
Meantime I'm looking at Perl/Qt (nice looking design tools, but what a name - Puic !?).
Then I'll look at Glade/Gtk, sounds interesting.
thanks & regards
Rod