Steve McMahon ha scritto:
I think Wichert's right about the basic implementation. If anyone's
interested in taking this on soon, I've got some ideas on the details.
Otherwise, it's on my to-do list!
I think that adding a storage somewhere (session or in the request), per
form, would be better instead of copyng fields and looking around.
Anyway, the reference is from the form one is coming from, or a fixed
one? That's because next step would be conditional jumps (if I answer
yes to a question, I would like to go directly to page X) :)
On Sun, May 10, 2009 at 10:04 AM, Wichert Akkerman <[email protected]> wrote:
Previously Martin Aspeli wrote:
Hi,
We're using PloneFormGen with a multi-page form as described here:
http://plone.org/products/ploneformgen/documentation/how-to/create-a-multi-page-form
There are three things I'd like to do, and I'm wondering if anyone's
either attempted this or have thoughts on how hard it'd be to do.
1) Repeating each field and making them hidden is a bit of a pain. I
was wondering if it'd be possible to create a new type of field that'd
basically just collate all fields from the previous request (i.e. all
values in the request less any fields on the current form) and passed
them along as hidden fields. Would that be feasible?
I once suggested to Steve to add a previous-form reference to a form. If
that was set PloneFormGen would follow the reference and copy all fields
over as hidden inputs. This is similar to your idea, except it would
put the setting on the form itself, which is a more logical place to put
it imho.
Wichert.
--
Wichert Akkerman <[email protected]> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
