I think a custom tag is going about it the wrong way... extra processing time,
limited formatting...
Why not write a form generator? Creates the CF code for you, then you just
tailor? What would be even better is if its generated code were delimited into
sections, and it could detect if you inserted extra code, so if you changed the
formatting, you wouldn't lose your custom code.
David Cummins
Peter Theobald wrote:
>
> So the real trick is making it extensible so you can use it to lay out a "basic
>default" form, but override certain things to customize it.
>
> The design I had worked out didn't assume you only had one field per row. It let you
>put as many fields as you liked in a row. It would add up the number of fields on
>each row, multiply them all for a "common" denominator, and use that as the number of
>columns in a table. Each table cell would use rowspan to use up the appropriate
>space. Everything would come out neat and lined up...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
