S
Steve Richter
I am spending too much time thinking of nesting tables within tables to
get the form layout that I want.
a simple example:
Sub heading:
property text: entry field
property text: entry field
Sub heading:
property text: entry field
property text: entry field
In this case I am using nbsp; before the property text to get the
indenting effect I want, but that is too repetitive.
Sometimes I would like to split a form into two or more sub tables, one
beneath the other. But then I cant get the columns of the tables to
align with each other.
Another issue is switching a form from display mode to entry mode. My
solution there is one set of input boxes are visible in change mode,
another set of label controls are visible in display mode. But that is
too many controls, each with an ID, having to be marked visible or not
in the code behind.
I can think of solutions to these issues using server controls, but as
much as I like to do that sort of thing, that approach does not earn me
any money and has brought me to the edge of financial ruin!
Do I just have a mental block when it comes to web form layout. Does
ASP.NET have a simple property sheet control? Too often I end up with
tables within rows within cells within tables that results in a rats
nest of parallel html and code behind.
what can I say. What book have I not read? Does CSS address this sort
of thing? I notice CSS does not address html tables much. Is there a
good reason for that?
thanks,
-Steve
get the form layout that I want.
a simple example:
Sub heading:
property text: entry field
property text: entry field
Sub heading:
property text: entry field
property text: entry field
In this case I am using nbsp; before the property text to get the
indenting effect I want, but that is too repetitive.
Sometimes I would like to split a form into two or more sub tables, one
beneath the other. But then I cant get the columns of the tables to
align with each other.
Another issue is switching a form from display mode to entry mode. My
solution there is one set of input boxes are visible in change mode,
another set of label controls are visible in display mode. But that is
too many controls, each with an ID, having to be marked visible or not
in the code behind.
I can think of solutions to these issues using server controls, but as
much as I like to do that sort of thing, that approach does not earn me
any money and has brought me to the edge of financial ruin!
Do I just have a mental block when it comes to web form layout. Does
ASP.NET have a simple property sheet control? Too often I end up with
tables within rows within cells within tables that results in a rats
nest of parallel html and code behind.
what can I say. What book have I not read? Does CSS address this sort
of thing? I notice CSS does not address html tables much. Is there a
good reason for that?
thanks,
-Steve