Re: Panel/Div/Table Overhead Costs
- From: "Marc " <RmEaMrOcVE@xxxxxxxxxxx>
- Date: Tue, 29 Jul 2008 21:40:40 +0100
"randy.buchholz" <randy.buchholz@xxxxxxxxxxxxxxxx> wrote in message
news:esXBRkO8IHA.1568@xxxxxxxxxxxxxxxxxxxxxxx
I'm trying to standardize a layout methodology for our agency and am
looking for some guidance. Most of the applications are basic store and
retrieve types, and extensively use a DetailsView type of layout. Almost
all fields have validation and formatting, and I have given up on details
views since I have to convert most fields to template fields for layout,
and use findcontrol to access the fields. I understand that HTML tables
are discouraged even though (I believe) the final output uses tables. I
use themes and CSS to do much formatting, but need a way to build
table-like layouts. I am thinking of using many div's or panels to create
a "grid" and CSS to control size, etc.
A Panel is just a DIV you can control behind the scenes (such as change it's
size, assign different CSSCLASS values and make invisible)
On the tables issue, if you are displaying tabular data then use a table. If
you are laying out the content of your page then use DIVs (or Panels).
I recommend you read a book on CSS before even starting to code C# or VB.
You may find it an idea to create different aspects of your pages in User
Controls (each within their own internal panel) and then place them onto
your page or master page. This makes a large page easier to manage
Marc
.
- Follow-Ups:
- Re: Panel/Div/Table Overhead Costs
- From: Munna
- Re: Panel/Div/Table Overhead Costs
- References:
- Panel/Div/Table Overhead Costs
- From: randy.buchholz
- Panel/Div/Table Overhead Costs
- Prev by Date: Connection Pooling
- Next by Date: Re: Building SQL connection string in code-behind file. Works on my machine, not on server.
- Previous by thread: Panel/Div/Table Overhead Costs
- Next by thread: Re: Panel/Div/Table Overhead Costs
- Index(es):
Relevant Pages
|
