Although not experimental, the results have not been exercised as much
as the other parts of the code. If there is missing functionality or
things that dont work, please ask or report bugs.
The original FormHandler process method, when used with persistent forms,
leaves behind state data for a particular execution of process. This is
not optimal or clean from an architectural point of view.
The intention with the result object is to separate dynamic data from static.
The form object is treated as a kind of result factory, which will spit out
results and leave the form in a consistent state.
In the current state of implementation, the result object can be used to render
However there are still open questions about how much of the form/field
should be forwarded to the result. At this point, the number of forwarded
methods is minimal. Mechanisms to make this more customizable are being
Dynamic select lists are not supported yet. Static select lists
(that are the same for every form execution) should work fine, but lists
that are different depending on some field value will not.
Most of this object is implemented in HTML::FormHandler::Result::Role,
because it is shared with HTML::FormHandler::Field::Result.