Re: Hiding the DOS window on Win32

The easiest and slickest way to do this is to use perl2exe with the -gui option. To get this feature you have to pay for the Pro Edition, but it's not expensive. Plus you get the additional benefit of cramming your whole app into one exe that can run on another computer with no external dlls, no libraries -- no nuthin' else. It's all embedded in the exe. And that means no install program. Just unzip and go. (A fairly large app, when zipped, will fit on a 1.44MB floppy.)

Sorry if this sounds like an ad, but I use the program and like it a lot.

Comment on Re: Hiding the DOS window on Win32

Replies are listed 'Best First'.
Re: Re: Hiding the DOS window on Win32 by the_slycer (Chaplain) on Nov 17, 2000 at 09:18 UTC
I have used this (only the text version registered), but the problem is the size. Consider, an app written with perl/tk, using the tk::text extension, 1.8 meg. That's a big binary to be running! (at least IMHO) And again the cross platform stuff comes up, I'd rather just pop the script out and let it be, it looks like the way I'm going to go is run the code to hide the window if the OS is windows. Why it took someone else to point that out I'll never know :-) (BTW - thanks Adam)	[reply]
Re: Re: Re: Hiding the DOS window on Win32 by Dr. Mu (Hermit) on Nov 18, 2000 at 00:11 UTC
I take your point. But perl2exe does offer a -tiny option in the pro edition that allows you to strip out some of the dlls and distribute them separately, which is an advantage if there is more than a single program involved. The questions one needs to ask when considering perl2exe are: 1. Will the program be run on just the development machine or be distributed to other machines as well? If the latter, how much trouble is it going to be to do a full Perl install on the other machines? 2. How "upgrade resistant" is the program? This is to say, if you upgrade your Perl installation, will the program have to be tweaked to accomodate it? (This may be a big issue when Perl 6 comes along, and is always a concern when you are using third-party modules.) If so, perl2exe allows you to freeze a working version, giving you time to do the tweaking (or not) as you see fit. Well, I guess my comments have taken us a bit afield of the original question! And once again, I probably sound like a shill for perl2exe. I'm not, but it does solve some problems for me that I don't mind sharing. :-)	[reply]