Contenu connexe Similaire à Progressing and enhancing (20) Plus de Christian Heilmann (20) Progressing and enhancing2. Our job as web
developers is to
create working
solutions.
4. All they should get
is an interface that
works and helps
them reach their
goal.
5. They need and want
to fulfil a task - not
marvel at our
craftsmanship.
8. We tend to get
terribly excited
about things in our
little world.
14. “Ev
ery
Java bod
Scr yh
frea ipt as
ks t - on
urn ly
it of
f.”
15. d
n !”
g a s
ra day
d e
t es
ec h
p
ex es t
le ac
op rf
P e
“
in te
d r op
16. ns t he
m ea e
i Pa d a sw
“ T he de si gn
fw eb
en d o
ow i t.”
kn
19. “My
favou
HTM rite p
art of
L5 is
locati geo
on!”
20. erfu lp art
ost pow
“T he m sitions
S3 is t ran
of CS tion s.”
and an ima
22. But three out of five
people know that
76.3% of statistics
are made up on the
spot.
23. Let me tell you what
happens when you
give out truisms like
that.
24. Every time you say
things like that...
This dog will disapprove... ...and these will not get fed.
27. Ligh
tbox
in pu
re CS
S!
28. look like
hin gs that
T ows 95
ba dW ind
Can vas
nsa vers in
s cree scr ipt!
and Java
Now with fr
ee 100% me
mory use!
29. Even if we don’t use
the technology - we
call it a CSS3 or
HTML5 solution.
31. It is ironic that we
don’t plan for non-
JS environments
but for IE6
fallbacks!
38. If we build the
simplest solution
first we can enhance
it to whatever we
want.
40. A lot of “using
newest technology”
is a lame excuse for
not architecting our
solutions.
41. There are real issues
HTML5 and CSS3
need to solve:
★ Security
★ Hardware Access (Camera, Location, 3D
accelleration)
★ Native rich controls
★ Layout
★ Internationalisation
★ Accessibility
★ Rich Media (video, audio)
42. For now, your only
chance to build
good web apps is
progressive
enhancement.
50. Getting data from a
web service on the
server and
rendering out HTML
for CSS and JS to
access.
51. If you want to build
things for the web
you will need to use
all these
technologies.
53. We did this for IE6
and that is why
there are so many
bad web
applications out
there.
54. It seems to be
impossible to get
rid of IE6 because
of that - but I have a
solution!
56. Despite of what I
said earlier, there is
one filter we can
use to solve one of
our problems.
57. One of the most
pointless IE filters
ever created is
blur().
http://msdn.microsoft.com/en-us/library/
ms532979%28VS.85%29.aspx
60. If we build the
simplest solution
first we can enhance
it to whatever we
want.
65. Then we get some
“experts” to tell the
press that it might
be software fatigue.
67. That way we turn
IE6 from a technical
problem to a health
and safety issue!