Well bust mah britches and call me cheeky, on Thu, 24 Jan 2008 10:27:35
GMT mrcakey scribed:
Disagree strongly. See HM's *good* analogy of a pretty mug with a
badly designed handle / nearly everything Apple has ever done.
Ya mean the HM who's known for his inappropriate comparisons?
Anyway, the designer designs the mug with a handle in such a manner that
it's appealing. It has to work, too, so he makes it large enough so
that little Arne doesn't burn his pinky on the cup and strong enough so
that it doesn't break, etc. But _how_ it does these thing in the
designed form is engineering and the engineer is the one who must make
the already-designed product work.
I design a web page and I want it to work a certain way. I have to know
enough to know it basically can work that way and should if correctly
marked up. I then engineer the html and css (plus optionally other
things) to make it work the way it was planned to work. There may be
problems. Ie: FF does something wierd, non-standard with a certain bit
of markup or the designer didn't understand the exact nature of
"relative" or whatever. I, as the page engineer, must resolve this or
go back to the designer and tell him his design sucks. Maybe my
explanation is colloquial, but there are definitely 2 different concepts
here, something which is often unrealized and the cause of many
arguments.