generateshas_field 'start_date' => ( type => 'DateTime' ); has_field 'start_date.month' => ( type => 'Integer', range_start => + 1, range_end => 12 ); has_field 'start_date.day' => ( type => 'Integer', range_start => 1 +, range_end => 31 ); has_field 'start_date.year' => ( type => 'Integer', range_start => +2000, range_end => 2020 );
See also t/compound_field.t is example of HTML::FormHandler::Field::Compound<div><fieldset class="start_date"><legend>Start date</legend> <div><label class="label" for="start_date.month">Month: </label><input + type="text" name="start_date.month" id="start_date.month" size="8" v +alue="7" /></div> <div><label class="label" for="start_date.day">Day: </label><input typ +e="text" name="start_date.day" id="start_date.day" size="8" value="14 +" /></div> <div><label class="label" for="start_date.year">Year: </label><input t +ype="text" name="start_date.year" id="start_date.year" size="8" value +="2006" /></div> </fieldset></div>
Does that makes sense?
From your example I can't tell what you want to become legend/fieldset. If you could explain that, then it might become clear if HTML::FormHandler needs patching, or if you need to create your own renderer or something else :)
FWIW, fieldset/legend doesn't look all that useful to me
In reply to Re^3: HTML::FormHandler rendering
by Anonymous Monk
in thread HTML::FormHandler rendering (somewhat SOLVED)
by CountZero
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |