Charlotte Foust
cfoust at infostatsystems.com
Tue Aug 11 10:26:41 CDT 2009
In web-based/browser-based apps, the client is sometimes allowed skins, and that's about as far as his preferences over the UI are considered. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Tuesday, August 11, 2009 4:10 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] SPAM-LOW: Zoho Access Migration Plugin Also known as thin client or dumb terminal (for a reason) from 30 years ago. And the pendulum swings... You left out all of the negatives however: 1) Dozens of technologies 2) Server load 3) Integration issues 4) UI clumsy to say the least 5) User UI preferences harder to deal with and so forth... John W. Colby www.ColbyConsulting.com Arthur Fuller wrote: > IMO this discussion is more properly framed not under "Web > development" but under "Browser-based development". Whether or not > your app talks to the world, if it has a bunch of users even all > sitting in the same offices, there are obvious advantages to going > with the browser-based paradigm, including but not exclusive to: > 1. updates are instantaneous -- no copying to each machine or anything > silly like that. Fix it in one place and presto -- the users see the > fix on their next click. > 2. support for mixed computer platforms -- Windows, Vista, Leopard, > Linux, who cares? > 3. UI consistent with stuff they (probably) already know. > > A.