Oh, and sorry for not including this in my other email, but upon looking over 
the code quickly, I just want to throw this in:

Non-table design does not work exactly like table based design.  For example, 
that top graphic was three slices in a table, but in CSS, it can be a single 
image.
Yep the top graphic is 3 images, as that is how the original was when I took over the project.
That top row of buttons really ought to be in a list.  It doesn't HAVE to be 
(what you have works), but semantically it probably would work better as a list.
I agree with the list item. I actually use lists in all of my layouts that flow like this, but I wanted to get the layout to look good. Eventually it will all be pulled from a database, so the list is where we are headed.
In fact, I would just basically toss all the Imageready code entirely and try 
marking it up from scratch.  It seems like an insane route to go, but 
Imageready is treating it as if it were a table-based layout.
The Imageready code is still there as I wanted to get something onine before I left work, so I could get all of your opinions, it will be stripped soon enough.

The sheer number of <div>'s with {position: relative; float: left} suggests that it 
would be much better just to go div   {position: relative; float: left} and override it for 
<div>'s that don't need it.
I agree on this point. I still have a few divs in the css document that I have not gotten to eliminate yet. I was going to start from scratch but decided to use their GoLive CSS output and after halfway realized it would have been faster to go from scratch.

<snipped>

Also, I will remove that space. I never noticed it. I have noticed that a space would cause all kinds of problems. I will see what I can find out.

Thanks for your help, I hope I get the go ahead to set up the database and the list items for this.

Zonjai
--
zonjai.com
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to