With regular apps, you can always use certain keystrokes to reach some goal, and thus, speeding up the use of the app tremendously. I don't see how you could build that into a website
Web apps tend to be simple enough that hot keys usually don't make sense. If your web app isn't simple, it probably shouldn't be a web app (HTML doesn't handle complexity well).
Ain't it lovely to pipe certain output to the next app?
Piping is just a means for programs to share data with each other. In a web app, the sharing is usually done by an RDBMS. If you really want to use a pipe, use wget or lynx -source to get the page printed to STDOUT. Certainly, this is far more likely to work than attempting to pipe a traditional GUI program.
Back button can annoy ...
Yup, that's a problem.
----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer
: () { :|:& };:
Note: All code is untested, unless otherwise stated
In reply to Re: Re: web-based application or desktop application?
by hardburn
in thread web-based application or desktop application?
by pg
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |