Hello all.
Interesting point of view.
Mr. Tom. Could you be so kind to explain a little about what tools
are you using? only CSS/Jvascript and maybe PHP, Rubby om Rails or
what. And as a datbase I can imagine you use Mysql , pPostgress or similar?
Just in case, if you need an application that needs to be local,
because sometimes your final user does not have Internet access (yes
there are some pleaces like that here). And you need to sync once in
a while with a central system , web based or not, what would you use?
I imagine that for your work not web based (5%) that you use RB. Habe
you thought to develop a mixed application that works locally and as
interface with abased system?
Thanks in advance for all your comments to all.
Jorge Biquez
At 04:42 p.m. 29/06/2009, you wrote:
For me, the only advantage of an app based solution is printing and
other HW interfaces... You don't need to show a print setup box in an
app to trigger a printer, so I still use RB for things like Point Of
Sale etc...
95% + of my work is now web based, basically because it can actually
realise the write once, deploy anywhere dream (mac/pc/mobile phone/
iTouch)... and it's only going to get better...
If you can exclude Internet Explorer as a deployment target, then life
will be a dream....
I've written versions of most of my RB controls in CSS/javascript, so
I can even give my web apps a native OS X app feel (and when I deploy,
I often recommend a fullscreen/kiosk browser like Plainview)
- Tom Benson
---------------------------------------------------------------
Custom Controls & Code Libraries
for REALbasic version 5.5 and up
http://www.qedit.com.au
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. If there
needs
to be a lot of processing on the data done, and I'm concerned about
server
load, then I'd use some javascript to handle most of that. It also
makes
your app incredibly accessible, especially if you deploy a version for
mobile browsers. No need to worry about people using old versions or
cheating on their licenses either. Ok, a lot less need anyway.
So.. a line though... I'm not really sure. Offhand I'd say it comes
down
to how large, in terms of memory footprint, the data your app would be
handling at any one time is. Obviously the larger it is the more
you'll
feel those network bottlenecks.
Just my two cents. I mean, I've never released a commercial desktop
application, so grain of salt, YMMV, etcetera.
Best,
Fargo
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|