lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV lynx and tables


From: Scott McGee (Personal)
Subject: Re: LYNX-DEV lynx and tables
Date: Sun, 12 Jan 1997 14:10:30 -0700

Al Gilman <address@hidden> writes:
>
>  From: Lucas Wolenczak <address@hidden>
>  
>  I want to make these pages at http://www.dal.net/servers/usa/texas.html
>  (for an example) lynx friendly with tables - what's the best way to go
>  about this, I've toyed around for a while now with it and I cant find an
>  acceptable solution - ideas? 
>
>You might want to peruse what Scott McGee has done at www.slcc.edu .
>For example, the calendar.
>
>Scott, what was it you used <TAB>s on?

(sorry for the delay responding, I was out of town for an Intranet Seminar.)

The Calendar page (http://www.slcc.edu/calendar.html) is an example of using
a table with embeded <P> tags to make things come out well on Lynx. The one
with the <TAB> tags is the Lynx FAQ (at http://www.slcc.edu/lynx/).

The Calendar page has the advantage of letting you use <TABLE> to format for
GUI browsers, while letting you use more traditional formatting for Lynx. The
FAQ page won't pass verification because of the <TAB> tags, but lets you use
the <TAB> to force a table like representation. IMHO, <TAG> is better than
using &nbsp; to handle formatting of this type but the Calendar page approach
it probably more general, and definately easier to read.

Scott

Scott McGee: Salt Lake Community College Webmaster | When in danger,
___________________________________________________| or in doubt,
Email: address@hidden (Scott McGee)         | run in circles,
Web:   http://www.slcc.edu/infotech/webmaster.html | scream and shout.
----------------------------------------------------------------------
My opinions do not necessarily reflect those of the College. Trust me!
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]