On Thu, November 17, 2005 2:06 pm, operationsengineer1@yahoo.com said:
> --- "Obe, Regina DND\\MIS"
> <robe.dnd@cityofboston.gov> wrote:
>
>> One of the key benefits of a web app is that as long
>> as you stick with W3
>> compliance, your web app will work on any
>> browser/OS.
>
> i wanted to add that is not my experience. there are
> so many hacks required to achieve cross browser
> compatibility it is AMAZING.
I just wanted to but in that I've done enough web development to have had
both experiences.
In general I've found that if you don't mind a little bit 'loose'
structure it is quite easy. The tighter your tolerances for placement,
the harder it gets.
(Then of course there are things that just aren't possible on one browser
or another.)
> the #1 problem, by far, is that not all browsers
> support w3c specifications... ie being the worst.
>
> at least in my experience.
True that. ;) The next version of IE is apparently *much* improved in
that regard, so in five-ten years when it has replaced enough of the
current browsers we'll be in good shape.
To the original poster: While you could do this in a web interface (and,
as I said, Ruby on Rails looks great for trying it...), I'd suggest you
not, unless you really are thinking of this as a client-server model, with
mutiple clients using it at the same time.
Daniel T. Staal
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------
