Re^2: Tk vs browser-based applications

Thanks, Errto!

When you say browser-based, do you mean the app runs on a web server and the user accesses it from a browser

That's what I have in mind, which means apache would need to be installed on user's computer.

How is it different from GUI with HTTP::Daemon?

Comment on Re^2: Tk vs browser-based applications

Replies are listed 'Best First'.
Re^3: Tk vs browser-based applications by Errto (Vicar) on Jul 05, 2005 at 04:08 UTC
I don't recommend distributing Apache for use in an end user desktop app, basically because it's overkill. The node I linked above describes a way to build the web server into your Perl program so that when the user runs it, the embedded web server starts and then the user's browser simply points to it. It's a pretty elegant solution in my view, which is why I used it in the app mentioned in my home node.	[reply]
Re^4: Tk vs browser-based applications by kiat (Vicar) on Jul 05, 2005 at 07:50 UTC
Hm...I copy and pasted the code at GUI with HTTP::Daemon and then ran it by double-clicking on the script. The perl interpreter was started and all I could see was the Dos box with C:\perl\test\pizza.pl as the title. Am I missing something?	[reply]
Re^5: Tk vs browser-based applications by Joost (Canon) on Jul 05, 2005 at 13:24 UTC
You should probably start a browser and look at the generated output - http://localhost:1234/ or some such URL :-) "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^6: Tk vs browser-based applications by kiat (Vicar) on Jul 05, 2005 at 13:44 UTC
Re^7: Tk vs browser-based applications by Joost (Canon) on Jul 05, 2005 at 21:56 UTC
Some notes below your chosen depth have not been shown here


Syntactic Confectionery Delight
	PerlMonks