[Seaside-dev] nested form handling

[Lukas Renggli]

As I said, you might want to create your own WAFormBrush subclass.
This is very unlikely to become default or go into the core though,
normally one should care where the forms go.

Lukas

On 10/6/08, Randal L. Schwartz <merlyn at stonehenge.com> wrote:
> >>>>> "Lukas" == Lukas Renggli <renggli at gmail.com> writes:
>
>  Lukas> Silently pruning nested form tags only works in most basic cases.
>
>  Right.  And I'm suggesting that if it works in 80% of the cases,
>  can we just teach Seaside to do that out of the box, along with a
>  warning in the WAFormBrush docs?
>
>  And I agree, I'd like to naively put a form around the outside of my entire
>  page, but then I can't create reusable components, because I'd have to have
>  two versions or require the invoker to always call it with a wrapper form,
>  which is inconvenient if they're in a callback rather than a rendering phase.
>
>  I'd settle for the WAFormBrush making it testable as to whether I'm in a form
>  already or not.  Can you make "html currentForm" return some form object or
>  nil?  Then my child components could test it and generate their own form if
>  not within one already.
>
>
>  --
>  Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
>  <merlyn at stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
>  Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
>  See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
>


-- 
Lukas Renggli
http://www.lukas-renggli.ch