I think that the main goal of (html) tables is to render tabular data;
for this reason using them to render a list is fine, but we should
avoid (if possible) to use them to render forms of type single.
Jacopo
On Jun 1, 2008, at 2:57 PM, Adrian Crum wrote:
Having the form layout change like
Having the form layout change like you suggested would be a cool feature.
Couldn't we have a widget attribute that controls that, and still output a
table? Something like field-label-orientation=top | bottom | reversed.
-Adrian
David E Jones [EMAIL PROTECTED] wrote:
I still like the idea
Hi,
There has been some momentum recently to add Ajax/Effects goodies to
HTML rendered using Screen/Form widget. I think as a part of this
effort we should consider moving away from FORM Layout using html
tables. The form layout using flexible html structures like div and
CSS can be made
I did some work on this years ago doing a prototype of sorts in the
newcustomer.ftl page. This is for single type forms only, as for list
and multi forms a CSS layout doesn't make sense (given the tabular
nature of that layout).
The important CSS classes are form-row, form-label, and
I remember CSS classes like col-row, col-left, col-right, etc. Basically tr
and td elements were replaced with div class=col-row and div
class=col-left - which made no sense at all. It was a lot of markup to do
nothing more than create a table.
Table layout is NOT evil - it is ideal for laying
I still like the idea because these aren't really a table per-se, ie
no natural columns and rows, just title and field sets. Some might
want the title above the field instead of to its left. Others might
want it below or to the right (because they are crazy I guess... ;) ).
Some might
David,
Thanks for adding details. For more complex data entry forms like
customer, I like to use ftl because we can do Two column layout and
have Web Designer make it look the way customer may like most.
Let's say if Shipping and Billing address are shown side by side and I
want to hide
