Have a look at the Views Theme Wizard. In recent versions, it is a multi-step form that uses the values from step 1 to generate form step 2. Step 2 (or sometimes step 3) has no submit buttons on it, but its content is the result of the previous steps. The last step then is the display, and there's no reason why you can't use form fields of #type markup to show just HTML that was built off of the previous steps.
Not sure if I'm on the same page as you, but I need to have a form
that has some input fields and a submit button, and when it's
clicked, the form passes the input to itself (or another page) and
then displays a table of results from a query (that I've created).
Any idea?
On 06 Feb 2008, at 8:59 PM, Ivan Sergio Borgonovo wrote:
Maybe there is a clean way to recycle most of FAPI if you don't need
to save anything in _submit but if you'd just like to produce some
output based on form input?
eg. you've 2 fields and the form "landing" page should display the
product (the landing page may still be the form path itself).
If there is such a technique that let you intercept $form_values and
$form_id outside _submit _validate and display output accordingly I'd
be glad to know.
Otherwise I'd really enjoy to see a _display hook that in spite of
showing the form or redirecting somewhere else would just have access
to $form_id and $form_values as _validate and _submit but would
output something else other than the form.
--
Ivan Sergio Borgonovo
Kind Regards
Graeme McKibbin
Software Developer