in reply to Tk vs browser-based applications

When you say browser-based, do you mean the app runs on a web server and the user accesses it from a browser? Or do you mean something like GUI with HTTP::Daemon, where the app runs on the client but works through an embedded web server? The server method gives you control over the platform, relieves you from worrying about people stealing your database password, and eliminates the effort of code distribution, but requires you to have a web server. If you mean the embedded app, then the difference between web and Tk is only in the interface, and frankly I'd go with whichever you're more comfortable building interfaces in. For me it's probably web.

Replies are listed 'Best First'.
Re^2: Tk vs browser-based applications
by kiat (Vicar) on Jul 05, 2005 at 03:52 UTC
    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?

[reply]
      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]
        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]

In Section Seekers of Perl Wisdom