I am on the other side of it.
I find web apps to be unsightly, slow, and awkward because they run in
a browser which is unsightly, slow, and awkward.
So I write apps that run over the internet as desktop applications.
Examples would be:
Online timecard submission for consultants.
Campground reservation system and credit card authorization.
Cash Register and Inventory systems.
Timecard and Payroll systems.
Database management tools.
Almost everything I write is database related.
If you write for web, you need to write for at least 3 browsers, each
of which is in a different state of compliance with the most recent
web document model. And then some users are not using the most recent
version of their browser type.
But on my desktop app, I can get it to look and behave the same way
for everyone.
Using a lot of custom controls, of course...
Rick
Rick Praetzel
Desert Sand Software
www.desertsandsoftware.com
RB 2008r5.1 Dual 2.5 GHz G5, 5GB RAM, OSX 10.5.7
MesaMySQL database browser/editor
MesaSQLite database browser/editor
On 30/06/2009, at 3:39 AM, fargo@rpgportland.com wrote:
Hi All,
Where would you draw the line between making a web based app or an
application ? Then of course I am talking about a database app
not like a
idvd / photoshop.
Best regards,
Trausti
For me, being primarily a web guy, if it boils down to some form
inputs/outputs then it's no-contest, web site all the way.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|