Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

Re: web-based application or desktop application?

by davido (Archbishop)
on Dec 04, 2003 at 05:14 UTC ( #312097=note: print w/replies, xml ) Need Help??

in reply to web-based application or desktop application?

The thing about doing it "web based" is that you get to take advantage of the fact that browsers already know how to understand markup (ie, various types of formatting), and most browsers have built-in "print" functions for creating hard copies.

This enables the developer to ignore issues such as dealing with printer output, dealing with event handlers, Tk callbacks / window management, etc.

So the development time is greatly reduced, while being able to present any feature a browser is capable of offering. Look at it like someone's already created an easy to use interface system. Yes, you still have to design the HTML that drives the interface, but that can be trivial as compared to dealing with a full fledged GUI.

Designing an application, and choosing to make it web based (intranet, etc.) is simply a design choice whos goal is to provide a lot of features with a minimum of development effort. Yes, a desktop based software package can be made to look even more polished. Heaven knows, nobody would really like to be forced to manipulate a web-based interactive spreadsheet. Nobody's going to suggest trying to come up with a web-based alternative to QuarkExpress, or Aldus Pagemaker. But if the objective lends itself to a web-based environment, there are good arguments for going that route.


  • Comment on Re: web-based application or desktop application?

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://312097]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (4)
As of 2018-04-22 11:05 GMT
Find Nodes?
    Voting Booth?