| |
I use
tables extensively, but strive to the keep table structure
as simple as possible for maximum performance. I use imbedded
tables to gives me paragraph and list spacing not available
otherwise. Notice the slight spacing between elements of
this bulleted list and its header. It is actually a table
without a border. The navigation bar at the top of the page
is a bordered table. Above that, the University logo, page
title and headings are in another table. The footer contact
information is a single row, two cell table.
In addition
I use a "primary" single row, single column table
to constrain the width of the page to approximately 620
pixels. The length of the table is not constrained. I place
all of my content within this table for the following reasons:
| 1) |
Although
in this day and age there are17" plus monitors
capable of running at 1280 X 1021 pixel resolution available,
one can not assume all visitors own one. Some may even
choose to run at lower resolutions for other reasons.
In general, one should consider the expected audience
and set the size accordingly. Programming for 600 X
480 pixels accomodates the most monitors currently in
use. However, it seems most professional sites are formatted
for 1024 X 800 resolution moditors. |
| 2) |
There
is also a "consumer" issue. As we move to
the future and to higher resolutions beyond current
standards become available, where do we draw the line
in the space we consume on the visitor's desktop? I,
for one, hate it when some web developer decides that
his site would be better viewed in full screen mode
and forces my browser to that mode. Or - even worse
- changing the size of my browser window after
I've carefully adjusted it to see my movie in the window
beside it. (That's why I bought that high res monitor
for in the first palce!) |
| 3) |
Just
as importantly, I can control how the content will appear
if a visitor chooses to print the page. 640 pixels is
about the right width for a typical default printer
setup, portrait mode. This assures that the visitor
gets the information they wanted to print, increasing
customer satisfaction. Formatting to the printed page
also keeps the application window to a great size for
those who favor windows view as opposed to full-screen
view users. |
However,
using Dreamweaver to create tables is problematic. I find
I have to modify the code directly in order to adjust the
tables properly and I'm still learning the details here.
|