On Wed, Aug 6, 2008 at 8:42 AM, 8bits Media
[EMAIL PROTECTED] wrote:
We currently have a project that includes a calendar in the design. The
dilemma I currently have, is what is the best way to mark the calendar
up?
Should we use tables, or is it more semantically correct these days to
use
We currently have a project that includes a calendar in the design.
The dilemma I currently have, is what is the best way to mark the
calendar up? Should we use tables, or is it more semantically correct
these days to use an unordered list?
I'd be very interested to here peoples thoughts
8bits Media wrote:
We currently have a project that includes a calendar in the design.
The dilemma I currently have, is what is the best way to mark the
calendar up? Should we use tables, or is it more semantically correct
these days to use an unordered list?
I'd be very interested to
theres a good standards based calendar tut here:
http://veerle.duoh.com/blog/comments/a_css_styled_calendar/
-best
kevin
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe:
There's a few different opinions out there, but I think I agree with
the responses from people on the list, tables make more sense. I
found this example of a calendar marked up using a list http://www.cssnewbie.com/list-based-css-calendar/
but I think I'll be using a table in this
Definitely a table for a calendar, like:
table
captionAugust 2008/caption
thead
tr
th scope=colSun/th
th scope=colMon/th
th scope=colTue/th
th scope=colWed/th
th scope=colThu/th
th scope=colFri/th
th scope=colSat/th
A table is a good option for static calendars. i.e a grid. On the flip side,
using a list based calendar, you'll be able to present it in different ways by
altering the style rules for the elements, e.g as a pseudo-grid, a list etc
etc.
And of course, there's no reason why you can't do both
