Tables and Divisions

[Harry]

...Tables are Tabular. Great for dynamic websites using php/mysql, but not for design....

No. Tables are great for tabular data. That's it.

It's messy and aggravating. Having to go to every page to change a layout through tables, and having to load an image, remove an image, etc. Annoying. That is why CSS was invented. To avoid having to work with frustrations of tables. If you don't learn CSS now, you will never learn how to properly and efficiently design a website.

Not really. It wasn't for development ease but for accessibility and better user experiences.

[lysol]

Its great for running dynamic data, for example, restaurant menu's, calendars, stuff like that.

[Harry]

No, do that with CSS and xHTML.

[lysol]

You can use tables for data, and for a small example, lets use a Calendar.

With that Calendar, you have rows and colums created with tables. You code it with css to layout the design, and use php/mysql for the dynamic data. Your page would be a php extension page. What does xHTML have to do with it?

[Harry]

A calendar is a great example. But the menu you mentioned shouldn't be done with tables. A menu is a list if anything.

[lysol]

True. But when you have a menu, even setting it as a list, its a pain to go into making changes, which is why its great to use PHP. The menu data is contained in the database, and all you have to do is go into your phpmyadmin, edit add, delete menu items. The table row becomes repeated, only 1 row. you don't have to create more rows or columns, it would just repeat the php code within 1 row without sacrificing more tabular mumbo jumbo.

just giving my personal opinion as its a pain to have clients call me and want to make changes. Why bother? PHP that website, and let them change it.

[Harry]

Yeah, style it in HTML, populate it with PHP. Just don't use a table for it.

[lysol]

---

ADVERTS - NOT VISIBLE TO MEMBERS

---

and i meant, a restaurant menu (especially big menu's). I hope I didn't confuse anyone.