Re^2: Conversion from Web script to stand-alone

That's because you need a HTTP server to process HTTP requests and spawn CGI scripts.

Probably the easiest way to get this to work quickly is to use a simple HTTP server like the one I pointed to in my post), especially since you're apparently still using a default browser to look at the HTML pages (IE just embeds in the explorer window if you have it as the default browser) - you could just as well make a perl (or .bat) script that starts the HTTP server and then points IE to the start-page.

But maybe I'm just misinterpreting what you're saying....

"What should it profit a man, if he should win a flame war, yet lose his cool?"

Comment on Re^2: Conversion from Web script to stand-alone

Replies are listed 'Best First'.
Re: Conversion from Web script to stand-alone by MonkPaul (Friar) on Aug 13, 2005 at 16:56 UTC
No not at all, you have the right train of thought going. I just was not sure if a module was capable of converting the script to a standalone package. I think the locally run server approach would be the best bet for this problem, though it means more fiddling with the host system. Not what i wanted but may have to suffice. I will look into the TK::HTML pages also to see what theyhave to offer. thanks guys and gals.	[reply]
Re^2: Conversion from Web script to stand-alone by Joost (Canon) on Aug 13, 2005 at 18:39 UTC
Well, if you want your system to run locally, you're going to have to "mess" with the system: you need to install some software, after all.. I also recommend you check out PAR. By the way, if at all possible, you should probably use a standard browser instead of Tk::HTML; it'll save you a lot of extra hassle, and users don't have to learn yet another browser. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]