Name: Anonymous 2009-02-02 16:28
I'm translating my fabulous Windows system console from C to Perl to make it support fancy features like inline input scripts based on eval(). There are some obstacles, though - mostly concerning about how to integrate it with system to mantain existing functionality.
I've tried Perl/tk and Win32::GUI. My impressions about Win32::GUI: it just sucks. It's deprecated, last version was released 12 months ago; furthermore, it doesn't even provide any elementary stuff like widgets' hwnd nor hdc. Also it doesn't coop with Win32::API providing its own set of functions instead - of course functions I need aren't implemented. There are some bugs too.
So I decided to pick up Perl/TK and Win32::Api.
The question is: is there any way to integrate perl/tk with windows messaging system, so my script will be able to communicate with system?
Or is there any TK engine providing support for both global hotkeys and communicating with external processes using, let's say, WM_COPYDATA (or anything else providing support for transporting long strings)?
I've tried Perl/tk and Win32::GUI. My impressions about Win32::GUI: it just sucks. It's deprecated, last version was released 12 months ago; furthermore, it doesn't even provide any elementary stuff like widgets' hwnd nor hdc. Also it doesn't coop with Win32::API providing its own set of functions instead - of course functions I need aren't implemented. There are some bugs too.
So I decided to pick up Perl/TK and Win32::Api.
The question is: is there any way to integrate perl/tk with windows messaging system, so my script will be able to communicate with system?
Or is there any TK engine providing support for both global hotkeys and communicating with external processes using, let's say, WM_COPYDATA (or anything else providing support for transporting long strings)?