o_19m7st4t316nvv6a1bg63l10e4a.pdf

Recommendations

Info

The Reader Often Crashes. As a final blow, Adobe's PDF reader program, for all its slowness, isn't even all that stable: it has a tendency to crash people's browsers after a while, especially if they try to use any of the browser's buttons. This upsets your visitors to say the least, and they're not likely to come back to your site again after their browser crashes because of your PDF. But They're Good for Printing. However, there is one area in which we have to give PDFs some credit. It's their original intended use: to preserve print layouts over the web so that they can be used for printing. If you want to give your visitors something that is best printed out on paper (a complicated graphical page, for example, or an official form), then the best way to make sure that it survives the journey across the web intact is to let them download it as a PDF. What does all this mean? Well, really, it means that unless you want to upset your visitors, the only time you should have PDFs on your site is when they're linked to like this: 'Download PDF (for printing)'. Any content you put in a PDF should always also be available as HTML. Why Java Will Drive Your Visitors Away. It's yet another plugin that users hate, and Java has an even worse reputation than most. Why? There are just so many reasons. Microsoft and Sun. Java is an open standard, and it's one that Microsoft originally embraced. They made their own Microsoft JVM (Java Virtual Machine) part of Internet Explorer. This led to the rapid growth of Java on the web. Sun, Java's creator, then decided to sue Microsoft, for being anti-competitive in bundling the Microsoft JVM with the world's most popular web browser. This was a bad move – Sun wanted Microsoft to bundle its JVM instead, but it actually led to Microsoft simply removing all Java support from Internet Explorer, and forcing users to go and download Sun's (from www.java.com) if they wanted to see Java content. The Web Design Guide for Newbies |152
That leaves us in the situation we're in today, where users can be divided into three groups: Users with old versions of Internet Explorer. They have the Microsoft JVM, which is wildly incompatible with Sun's. Users with new versions of Internet Explorer but no JVM. They don't have a JVM, meaning that you'll have to get them to download Sun's to see Java content – and Sun's JVM is a big download. Users with Sun's JVM. They're not only the smallest group, but they're also using a JVM that is incompatible with Microsoft's. This leads to a situation where you can either code for the smallest group of users (who have a supported plugin), or the next largest one (who have an unsupported one), or try to force the largest group (who have no plugin) to get one. This is obviously an extremely bad situation to find yourself in. The Speed Problem. Java's problems, though, don't end there. Even assuming that your user has one JVM or the other, they still won't want to use Java content. The big reason for this is that Java is very, very slow. How slow? It's slow to the point where going to any page that has Java on it will cause most browsers to freeze up for about 30 seconds or so, appearing to have crashed completely. Users are unlikely to be patient enough to wait for the Java to load, instead press control, alt and delete to get out of there. Java's adherents mostly refuse to acknowledge the speed problem, but it's bad enough that downloadable desktop programs written in Java have become a complete joke – anything useful written in Java will be pretty promptly re-written in someone else to make a more responsive and usable version. Java programs are simply impractical thanks to their speed problems, and no matter how fast computers get it doesn't seem to get any better. The Looks Problem. The Web Design Guide for Newbies |153
Page 2 and 3:
ABOUT WEB DESIGNER PAD Web Designer
Page 4 and 5:
Chapter 1: Why You Need a Website?
Page 6 and 7:
Chapter 2: How the Web Works. Many
Page 8 and 9:
Resource Location) while hosting is
Page 10 and 11:
cost. Prepared to be surprised by s
Page 12 and 13:
POP3 accounts. POP stands for 'Post
Page 14 and 15:
these), as well as the email addres
Page 16 and 17:
website to do. What kind of thing d
Page 18 and 19:
professionals, have you? Well, the
Page 20 and 21:
If you don't want to deal with desi
Page 22 and 23:
If you're willing to take the less
Page 24 and 25:
While Mozilla is a web browser itse
Page 26 and 27:
GIF stands for Graphics Interchange
Page 28 and 29:
As the web grew, the lack of standa
Page 30 and 31:
Now, though, you can remove the fon
Page 32 and 33:
intended on every web browser out t
Page 34 and 35:
the web without ever knowing a thin
Page 36 and 37:
out in the lead in terms of market
Page 38 and 39:
hire a professional web designer, o
Page 40 and 41:
graphics may be stored in the cache
Page 42 and 43:
Note that you will need to save fil
Page 44 and 45:
heading is, so h1 for a page's main
Page 46 and 47:
500 - Internal server error. For mo
Page 48 and 49:
easons. To begin with, there are tw
Page 50 and 51:
that come with Windows, they don't
Page 52 and 53:
What's So Bad About Tables? If you'
Page 54 and 55:
text-align. Lets you align text on
Page 56 and 57:
each down further than the main con
Page 58 and 59:
start growing, though, you might fi
Page 60 and 61:
the 'glue' that makes a database-dr
Page 62 and 63:
Basic-like language named VBScript,
Page 64 and 65:
Yet, despite how common databases a
Page 66 and 67:
Which Database is Right for You? If
Page 68 and 69:
Once you've created your website, y
Page 70 and 71:
that is how easy it makes it to cre
Page 72 and 73:
mysql_fetch_assoc. Turns the result
Page 74 and 75:
Separating the Application Logic. T
Page 76 and 77:
written by you or by someone else.
Page 78 and 79:
double-click. onmouseover. Runs whe
Page 80 and 81:
limits, and do more testing than yo
Page 82 and 83:
and no-one else supports it. For be
Page 84 and 85:
} } ajax = new ActiveXObject("Micro
Page 86 and 87:
is being used - useful when you see
Page 88 and 89:
on. Resizing works especially well,
Page 90 and 91:
provides almost every feature you c
Page 92 and 93:
on the Linux GTK (Gimp Toolkit) sys
Page 94 and 95:
Ikonboard (http://www.ikonboard.com
Page 96 and 97:
the other visitors - your role is t
Page 98 and 99:
asked for it. You should link to it
Page 100 and 101:
own. It's madness to pay thousands
Page 102 and 103: considering first, but you should b
Page 104 and 105: usiness with you. However, you shou
Page 106 and 107: the checkbox a name so you can refe
Page 108 and 109: same thing goes for lists of states
Page 110 and 111: One of the biggest issues with prin
Page 112 and 113: If you're about to write out a big
Page 114 and 115: don't hide anything from the people
Page 116 and 117: It's Not a Newspaper. What's the di
Page 118 and 119: color is a big subject. As soon as
Page 120 and 121: important in one way: the meta desc
Page 122 and 123: It's not difficult to switch betwee
Page 124 and 125: fonts.com and typography.com for a
Page 126 and 127: sets are red-green; blue-orange, an
Page 128 and 129: while sans-serif fonts have a tende
Page 130 and 131: Look at it this way: not only are y
Page 132 and 133: your content, or, worse, even hide
Page 134 and 135: sure that your design will work jus
Page 136 and 137: Smart Tags. Do you think it ends th
Page 138 and 139: This principle is even more importa
Page 140 and 141: Each option links through to anothe
Page 142 and 143: At this point, you'd have a big pro
Page 144 and 145: one key question you should ask the
Page 146 and 147: Now, when users hover over the prin
Page 148 and 149: come to associate its use with that
Page 150 and 151: tends to provoke is "hey, I was loo
Page 154 and 155: The next problem is the way Java te
Page 156 and 157: Here's something that many people d
Page 158 and 159: Trackbacks. Using blog software tha
Page 160: Chapter 38: Switching Web Hosts. Fi
show all

o_19m7st4t316nvv6a1bg63l10e4a.pdf

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?