- •Taking Your Talent to the Web
- •Introduction
- •1 Splash Screen
- •Meet the Medium
- •Expanding Horizons
- •Working the Net…Without a Net
- •Smash Your Altars
- •Breath Mint? Or Candy Mint?
- •Where’s the Map?
- •Mars and Venus
- •Web Physics: Action and Interaction
- •Different Purposes, Different Methodologies
- •Web Agnosticism
- •Point #1: The Web Is Platform-Agnostic
- •Point #2: The Web Is Device-Independent
- •The 18-Month Pregnancy
- •Chocolatey Web Goodness
- •’Tis a Gift to Be Simple
- •Democracy, What a Concept
- •Instant Karma
- •The Whole World in Your Hands
- •Just Do It: The Web as Human Activity
- •The Viewer Rules
- •Multimedia: All Talking! All Dancing!
- •The Server Knows
- •It’s the Bandwidth, Stupid
- •Web Pages Have No Secrets
- •The Web Is for Everyone!
- •Swap text and code for images
- •Prune redundancy
- •Cache as Cache Can
- •Much Ado About 5K
- •Screening Room
- •Liquid Design
- •Color My Web
- •Thousands Weep
- •Gamma Gamma Hey!
- •Typography
- •The 97% Solution
- •Points of Distinction
- •Year 2000—Browsers to the Rescue
- •Touch Factor
- •Appropriate Graphic Design
- •User Knowledge
- •What Color Is Your Concept?
- •Business as (Cruel and) Usual
- •The Rise of the Interface Department
- •Form and Function
- •Copycats and Pseudo-Scientists
- •Chaos and Clarity
- •A Design Koan: Interfaces Are a Means too Often Mistaken for an End
- •Universal Body Copy and Other Fictions
- •Interface as Architecture
- •Ten (Okay, Three) Points of Light
- •Be Easily Learned
- •Remain Consistent
- •Continually Provide Feedback
- •GUI, GUI, Chewy, Chewy
- •It’s the Browser, Stupid
- •Clarity Begins at Home (Page)
- •I Think Icon, I Think Icon
- •Structural Labels: Folding the Director’s Chair
- •The Soul of Brevity
- •Hypertext or Hapless Text
- •Scrolling and Clicking Along
- •Stock Options (Providing Alternatives)
- •The So-Called Rule of Five
- •Highlights and Breadcrumbs
- •Consistent Placement
- •Brand That Sucker!
- •Why We Mentioned These Things
- •The year web standards broke, 1
- •The year web standards broke, 2
- •The year web standards broke, 3
- •The year the bubble burst
- •5 The Obligatory Glossary
- •Web Lingo
- •Extranet
- •HTML
- •Hypertext, hyperlinks, and links
- •Internet
- •Intranet
- •JavaScript, ECMAScript, CSS, XML, XHTML, DOM
- •Web page
- •Website
- •Additional terminology
- •Web developer/programmer
- •Project manager
- •Systems administrator (sysadmin) and network administrator (netadmin)
- •Web technician
- •Your Role in the Web
- •Look and feel
- •Business-to-business
- •Business-to-consumer
- •Solve Communication Problems
- •Brand identity
- •Restrictions of the Medium
- •Technology
- •Works with team members
- •Visually and emotionally engaging
- •Easy to navigate
- •Compatible with visitors’ needs
- •Accessible to a wide variety of web browsers and other devices
- •Can You Handle It?
- •What Is the Life Cycle?
- •Why Have a Method?
- •We Never Forget a Phase
- •Analysis (or “Talking to the Client”)
- •The early phase
- •Design
- •Brainstorm and problem solve
- •Translate needs into solutions
- •Sell ideas to the client
- •Identify color comps
- •Create color comps/proof of concept
- •Present color comps and proof of concept
- •Receive design approval
- •Development
- •Create all color comps
- •Communicate functionality
- •Work with templates
- •Design for easy maintenance
- •Testing
- •Deployment
- •The updating game
- •Create and provide documentation and style guides
- •Provide client training
- •Learn about your client’s methods
- •Work the Process
- •Code Wars
- •Table Talk
- •XHTML Marks the Spot
- •Minding Your <p>’s and q’s
- •Looking Ahead
- •Getting Started
- •View Source
- •A Netscape Bonus
- •The Mother of All View Source Tricks
- •Doin’ it in Netscape
- •Doin’ it in Internet Explorer
- •Absolutely Speaking, It’s All Relative
- •What Is Good Markup?
- •What Is Sensible Markup?
- •HTML as a Design Tool
- •The Frames of Hazard
- •Please Frame Safely
- •Framing Your Art
- •<META> <META> Hiney Ho!
- •Search Me
- •Take a (Re)Load Off
- •WYSIWYG, My Aunt Moira’s Left Foot
- •Code of Dishonor
- •WYS Is Not Necessarily WYG
- •Publish That Sucker!
- •HTMHell
- •9 Visual Tools
- •Photoshop Basics: An Overview
- •Comp Preparation
- •Dealing with Color Palettes
- •Exporting to Web-Friendly Formats
- •Gamma Compensation
- •Preparing Typography
- •Slicing and Dicing
- •Rollovers (Image Swapping)
- •GIF Animation
- •Create Seamless Background Patterns (Tiles)
- •Color My Web: Romancing the Cube
- •Dither Me This
- •Death of the Web-Safe Color Palette?
- •A Hex on Both Your Houses
- •Was Blind, but Now I See
- •From Theory to Practice
- •Format This: GIFs, JPEGs, and Such
- •Loves logos, typography, and long walks in the woods
- •GIFs in Photoshop
- •JPEG, the Other White Meat
- •Optimizing GIFs and JPEGs
- •Expanding on Compression
- •Make your JPEGS smaller
- •Combining sharp and blurry
- •Animated GIFs
- •Creating Animations in ImageReady
- •Typography
- •The ABCs of Web Type
- •Anti-Aliasing
- •Specifying Anti-Aliasing for Type
- •General tips
- •General Hints on Type
- •The Sans of Time
- •Space Patrol
- •Lest We Fail to Repeat Ourselves
- •Accessibility, Thy Name Is Text
- •Slicing and Dicing
- •Thinking Semantically
- •Tag Soup and Crackers
- •CSS to the Rescue…Sort of
- •Separation of Style from Content
- •CSS Advantages: Short Term
- •CSS Advantages: Long Term
- •Compatibility Problems: An Overview
- •Working with Style Sheets
- •Types of Style Sheets
- •External style sheets
- •Embedding a style sheet
- •Adding styles inline
- •Fear of Style Sheets: CSS and Layout
- •Fear of Style Sheets: CSS and Typography
- •Promise and performance
- •Font Size Challenges
- •Points of contention
- •Point of no return: browsers of the year 2000
- •Absolute size keywords
- •Relative keywords
- •Length units
- •Percentage units
- •Looking Forward
- •11 The Joy of JavaScript
- •What Is This Thing Called JavaScript?
- •The Web Before JavaScript
- •JavaScript, Yesterday and Today
- •Sounds Great, but I’m an Artist. Do I Really Have to Learn This Stuff?
- •Educating Rita About JavaScript
- •Don’t Panic!
- •JavaScript Basics for Web Designers
- •The Dreaded Text Rollover
- •The Event Handler Horizon
- •Status Quo
- •A Cautionary Note
- •Kids, Try This at Home
- •The Not-So-Fine Print
- •The Ever-Popular Image Rollover
- •A Rollover Script from Project Cool
- •Windows on the World
- •Get Your <HEAD> Together
- •Avoiding the Heartbreak of Linkitis
- •Browser Compensation
- •JavaScript to the Rescue!
- •Location, location, location
- •Watching the Detection
- •Going Global with JavaScript
- •Learning More
- •12 Beyond Text/Pictures
- •You Can Never Be Too Rich Media
- •Server-Side Stuff
- •Where were you in ‘82?
- •Indiana Jones and the template of doom
- •Serving the project
- •Doing More
- •Mini-Case Study: Waferbaby.com
- •Any Size Kid Can Play
- •Take a Walk on the Server Side
- •Are You Being Served?
- •Advantages of SSI
- •Disadvantages of SSI
- •Cookin’ with Java
- •Ghost in the Virtual Machine
- •Java Woes
- •Java Woes: The Politically Correct Version
- •Java Joys
- •Rich Media: Exploding the “Page”
- •Virtual Reality Modeling Language (VRML)
- •SVG and SMIL
- •SMIL (through your fear and sorrow)
- •Romancing the logo
- •Sounds dandy, but will it work?
- •Promises, Promises
- •Turn on, Tune in, Plug-in
- •A Hideous Breach of Reality
- •The ubiquity of plug-ins
- •The Impossible Lightness of Plug-ins
- •Plug-ins Most Likely to Succeed
- •Making It Work: Providing Options
- •The “Automagic Redirect”
- •The iron-plated sound console from Hell
- •The Trouble with Plug-ins
- •If Plug-ins Run Free
- •Parting Sermon
- •13 Never Can Say Goodbye
- •Separation Anxiety
- •A List Apart
- •Astounding Websites
- •The Babble List
- •Dreamless
- •Evolt
- •Redcricket
- •Webdesign-l
- •When All Else Fails
- •Design, Programming, Content
- •The Big Kahunas
- •Beauty and Inspiration
- •Index
226 HOW: Visual Tools: Format This
text has less anxiety about the fact that some images may not have finished downloading. With sufficiently engaging text, the user will feel that the site is responsive. Keep this in mind when designing sites that require a great many images.
JPEG, the Other White Meat
The Joint Photographic Experts Group (JPEG) format should be familiar to you from stock photo houses, digital cameras, and the Photoshop tutorial itself. Usually seen with a .jpg file extension (as in landscape.jpg), JPEG supports 24-bit color and preserves the subtle hue and brightness variations found in photographs and other continuous-tone images. JPEG is therefore usually the format of choice when creating photographic images for the Web. Like GIF, JPEG is widely supported in visual web browsers.
Just as MP3 music files toss away audio harmonics to achieve compact file sizes, JPEG’s compression works by selectively discarding bits of image data. Because a loss of quality is involved, JPEG compression is referred to as lossy compression. “Lossy” is an annoying word that looks wrong, but we appear to be stuck with it. In theory, the material discarded by the JPEG optimization process is data that is nearly invisible to the human eye (just as audio data discarded by the MP3 format is supposed to go practically undetected by your ears, though we’ve never met a music fan who could not hear the difference). The greater the JPEG compression, however, the more visible the “missing data” becomes. At extremely high compression ratios, JPEG images can display funky artifacts (see Figures 9.5 and 9.6).
Although JPEG is generally preferred for photographic images, when sharp detail is important, GIF is the better choice. JPEG tends to soften images as it compresses them. Particularly when you are working with typography, the softness of JPEG images can ruin the effect of a web graphic. Naturally, there is a workaround, as explained in the “Combining Sharp and Blurry” section later in this chapter.
Unlike GIF, the JPEG format does not retain specific web-safe (or other) colors. It promises you a rose garden, but the rose might be umber. In a silhouetted portrait where the edges of the image must match the background of the web page, you would therefore use GIF, not JPEG.
Taking Your Talent to the Web |
227 |
Figure 9.5
At moderate JPEG compression levels, image details are clear, but file size is high.
Figure 9.6
At high JPEG compression levels, file size is low (minimizing bandwidth) but so is the quality. Each JPEG optimization is an exercise in balancing file size versus quality of detail.
228 HOW: Visual Tools: Format This
Photoshop’s Save For Web function provides a small, Matte Color dialog box that purports to save an exact background color of your choice, even in the JPEG format. (Skip ahead to Figure 9.7, if you must. The Matte Color dialog appears at mid-right.)
Photoshop does all it can to fulfill this promise, but the JPEG format really is not built to handle specific colors like this. To viewers with 24-bit and higher systems, the background color will appear to match. For 16-bit and lower users, the mismatch may be clearly visible. So stick with GIF when you absolutely, positively, have to deliver a specific web-safe (or other) color.
In Photoshop, you can choose whether to save your JPEG as a baseline (standard) JPEG or as a progressive JPEG. Progressive JPEGs display a lowresolution version of the image almost immediately and then gradually come into crisper focus.
As with progressive GIFs, under the right circumstances, progressive JPEGs can create the illusion that the site is loading faster. As previously discussed, this varies depending on the viewer’s access speed, browser functionality, browser preferences, and the caprices of HTTP. And as in the discussion of GIFs above, when intended as background images, progressive JPEGs are a no-no unless you want some of your visitors to crashcrash.
Optimizing GIFs and JPEGs
When we export images such as GIFs and JPEGs, we choose the format most appropriate to the type of image we’re dealing with and then optimize it to create the best appearance possible, while using the least amount of bandwidth and computing resources.
In addition to optimizing (reducing file sizes), the exporting process allows us to further exert control over the color of our GIF images.
Photoshop 3, 4, and 5 offered early web designers very little in the way of optimization and color controls. As a result, a number of inexpensive, third-party, shareware plug-in products specifically tailored to the needs of web designers sprang up in the mid-1990s, most notably Boxtop
Taking Your Talent to the Web |
229 |
Software’s PhotoGIF, ImageVice, and ProJPEG (all are available at www.boxtop-software.com). These products were dandy (still are), but they did not come as standard equipment (still don’t). Arguably, they do a better job than Photoshop at handling some tasks.
Fortunately, Photoshop 5.5 and higher, together with ImageReady, offers a number of tools to help web designers create the best-looking image while using the least amount of bandwidth. Photoshop’s Save For Web command (found in File, Save For Web) enables web designers to preview the effects of various compression settings on their images and then execute those settings and save the resulting web-ready images (see Figure 9.7).
The Save For Web dialog is powerfully compelling in the breadth and subtlety of its tools. You can preview GIF versions using as few as two colors, as many as 256, or anything in between. You can use Adaptive, Selective, Perceptual, or web-safe color, with or without dithering, transparency, or interlacing (the “progressive” setting). You can skew images closer to or further from the web-safe palette as you desire. You also can name and save custom settings for later application to similar images.
Figure 9.7
Photoshop’s Save For Web dialog in action. In this “four-up” view, the original image appears at the upper left for easy comparison with various optimization schemes of your choosing.
230 HOW: Visual Tools: Format This
Work on one optimization setting at a time or view three at once—and compare them with the original to check for image degradation and color shifting. Get an instant readout of the effect your decisions will have on
file size and downloading speed. Enlarge images to check fine details. Lock selected colors before trying a new set. Shift one color at a time to its closest web-safe equivalent. We feel like press agents. We feel giddy. We love this dialog box. You will too.
Images in Save For Web mode also may be previewed at various JPEG settings, both baseline and progressive, and again the tools are remarkably powerful.
In general, the fewer the colors used in a GIF, the better it compresses. This is not because the color palettes themselves eat bandwidth; rather it is because of the way LZW compression works. More on that in a moment in the “Expanding on Compression” section that is coming up next.
Dithering images produces more photographic-like effects at the cost of slightly higher file sizes; images without dithering are smaller. We find that typographic GIFs are often cleaner and more legible when saved without dithering. Your mileage may vary. You can create either type of image (and preview the results) in Photoshop’s Save For Web dialog box.
After you decide which optimization scheme works best for a given image, the image can be saved in that format. Your chosen settings may be retained indefinitely, and can even be applied (as a droplet) to an entire folder of images.
Photoshop lets you name and store as many of these settings as you like. If a series of images you’ve created for Acme Widgets happens to work well in 12 colors with no dithering at 60% web-safe, you can name that setting 12color_nodither (or acme_widgets or 60websafe or donaldduck if you prefer). You can then save it forever—or at least until your backup media deteriorates and what’s left of your hair is white and listless. By then we’ll all be living on Mars while our clones do the work, anyway.
Alternately, you can use the ImageReady module to satisfy your wanton image compression and formatting needs. But Photoshop’s Save For Web is just as effective, and the true power of ImageReady comes later in the process (and this chapter).