I'm working on a package where I cannot get ad_form to render the page in a way that makes sense. Simply put, I want the radio buttons to go across the page wrapped with some HTML to make the presentation more intuitive to the user.
I looked at template::form, and while it does allow more overall control, I still end up with a form that I cannot render as much as I would like.
If I roll my own, I can get the page to look exactly how I want, but, I lose out on some of the strengths of using the built in methods.
I run into another issue that I don't know quite how to handle.
I have 15 rows of data in Postgres, but again, for user aesthetics, I cannot figure out how to make this work using ad_form or template::form.
Basically I pull the data using a multirow, but, I want each line to be its own 'form'. I don't care if I have 15 submit buttons to allow a change and it calls one form, or if I have 15 forms. A simple diagram is here.
[select pulldown] ___________________ [save] [Delete]
The obvious benefit to having it be one form is that changes on multiple records aren't lost when they hit save, but how do I get ad_form to output and handle 15 rows from SQL? or is this more a job for template::form?