When I teach web development course, I emphasize the use of tables and show examples
of how using
simple table makes life easier to do some nifty things, especially in ASP.NET. For
instance, instead
of writing separate pages, I can have different parts of a page visible or invisible
by manipulating rows of
table, and in postback I can control what to display.
ASP.NET allows you to set runat="server" for pure tables and assign ids for row. This
helps to work with rows
on server side.
The problem with a table is it's not new, and it's not cool. However, it
works. This goes well along one
of the principles of agile development?to find simple solutions that actually work.
Sometimes I wondered if developers appreciate that emphasis or think I am crazy using
tables. I have to
wonder no more. I am convinced after reading Dion.
