To Open The Sky
The Front Pages of Christopher P. Winter
A few words about pictures in general
I appreciate a good image, and I will be posting some here. At the same time, I appreciate words, and I understand that there are times when words can communicate better — and more vividly — than any picture. I hope to demonstrate here that I can recognize both situations.
A lot has changed since I wrote the following three paragraphs:
The technical analysis has moved (I've updated the link above) and, while the most recent survey says the percentages of Web denizens using 16-bit and 8-bit color are down to 1% and 0.5% respectively, those are far from zero in absolute numbers of users. They undoubtedly represent less developed countries for the most part, but may also be concentrated in some areas or cohorts of the U.S.
Color-display systems for personal computers can be divided into three categories:
Web-safe colors were adopted as a cross-browser standard when 8-bit color depth was almost universal. The palette of 216 hues was chosen to minimize dithering, in which the browser tries to match a web-safe shade with one it does support. This can produce ugly cross-hatching. There is no guarantee that every browser out there supports the standard, and high-color systems have a completely different set of colors. I still use Web-safe colors commonly, though not in every case, and based on this I see no reason to stop.
It still adds up to what the Chinese might call "interesting times".
Web Page Design Standards
My goal is to design pages that work well at all resolutions, from the VGA standard (640 x 480, 256 colors) up through the high end (which I think means 32-bit color at 1280 x 1024). However, I work mostly at 1024x768 resolution, so you might find pages that don't look good on your screen. If you find such a case, I'll be happy to hear about it. Please drop me an E-mail and let me know.
I no longer use HTML frames at all, so there's no need for a <NOFRAMES> section anywhere on my site.
To accomodate text-only browsing and aural readout, I will always place an ALT tag in my image calls to tell those using text-only browsers what the image represents. And I will try to keep the size of my image files to the minimum compatible with clarity. (For JPEGs, the most common format on the Web, I've observed that anything below about 20k bytes often begins to look blurry or chunky.) Aural readers are likely to be poorly served for some time to come, since I'm just starting to learn about this mode.
My pages are now validated to HTML 4.01 Strict and CSS2 standards. There was one place where I launched a page in a new window, using the "Target" attribute of the Anchor tag; this required sticking with 4.01 transitional for that one page. There was no real benefit to it, so that's now gone. And you can call me a stick-in-the-mud if you like, but I'm sticking with static HTML.
The bottom line is: Although I've been at this game for over ten years, there might still be some rough spots in my pages. Bear with me. And remember that constructive criticism is always welcome.