Ricky, you are welcome to use ad_form (with ecommerce). I am not interested in blocking any progress on the code.
I wonder why /register/index and /register/user-new have to be on different pages?
Thank you for the ad_form explanation and demo/example. They *are* helpful. I am still quite wary to start using it, but am saving your info for reference. Perhaps I can tackle ad_form in the context of my familiarity with ecommerce package. I can see how it could be fun to one day re-code ecommerce/www/checkout-one-form*
Emulation is the best way for me to learn this. How would ad_form be coded to handle these common form requirements in ecommerce:
1. block double-clicks or re-submits after the form has been validated and posted
2. handle file-uploads
3. handle multiple date/time fields
4. lists of data in the form, much like the current thread: https://openacs.org/forums/message-view?message_id=2516549 but where the form includes entry for multiple columns as well as rows.
Combining ad_form and template::list seems really complex and yet could be used in many places in ecommerce. That's why I've bee working on code to combine ad_form, template::list, form generation (as web service or multiple browser entry styles or file upload/input), and templates (like AMS) at: http://dekka.com/p2/xowiki/ecks-forms to start with an elegant solution for the most complex which hopefully will make the other cases even easier.
In any case, I'm willing to work with ad_form and follow your lead.