On Fri, Jun 23, 2006 at 08:55:35AM -0700, [EMAIL PROTECTED] wrote:
> I'm thinking of doing a web app that could run
> locally if desired. I'd like to do *both* remote
> and local app with an HTML/browser interface.
>
> Why don't I see more open source apps using
> the browser as the interface?
>
> Even local apps could go to a URL like
> localhost:8080. Is something wrong with
> this that I'm missing?
>
> (I /really/ don't want to dork around with
> GTK+ and qt.)
>
> Chris
Because they're a PITA to write and debug? Because performance is
slovenly, even locally?
The only up side to a browser interface is that you don't have to
distribute your client. After that, everything is downside: security
(really, how many services can we shoe-horn over that abused port?),
complexity, performance, I would even say tool sets, although the
PHP/mySQL crowd would probably scream at me.
That said, if you just have to do it (PHBs demand it or you think it's
way cool and you can't stop yourself), by all means develop it locally.
With any kind of luck it should then work when you distribute it ... but
don't forget to test with lynx, IE, Opera, Mozilla, Firefox, etc ad
nauseam. Unless "it works on my browser" is acceptable wherever this is
for, which god knows seems to be the mantra in M$ shops..
Were I to do it (and I might have to someday soon), I'd recommend
looking at some simpler web server with good scripting hooks like
Tclhttpd. Apache has everything, which is good, but apache has
everything, which is bad. Avoiding javascript would be a primary design
goal for me.
--
Lan Barnes
Linux Guy, SCM Specialist
Tcl/Tk Enthusiast
Most undergraduate degrees in computer science these days are basically
Java vocational training.
- Alan Kay
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
