I'm -1 on allowing nested forms, and +1 on throwing a runtime error if this condition is encountered. Non-binding.
On 11/5/06, Korbinian Bachl <[EMAIL PROTECTED]> wrote:
shame on me ... now serious > I think the way we treat nested forms in 2.0 and 1.3 a real > improvement and a showcase for component frameworks: work > around problems in an elegant and meaningful way. Abstract > away the limitations of the protocols we have to work with. i think this is a big danger - remember: most wicket users come from a point of GUI building, they dont know the limitations of http, html, css, ajax - this ends usually up in trouble (security, locked out browsers, unusability, load, not barrer free...) my personal way is to always stick to standards - it might be harder sometimes to achive this, but youre on a save side... Regards Korbinian > -----Ursprüngliche Nachricht----- > Von: Martijn Dashorst [mailto:[EMAIL PROTECTED] > Gesendet: Sonntag, 5. November 2006 22:00 > An: wicket-dev@incubator.apache.org > Betreff: Re: Re: [VOTE] Nested forms - don't process inner > form fields in outer form submit > > On 11/5/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > The vote: don't process inner form fields when the outer form is > > > submitted [ ] Yes, don't process those pesky little > fields [ ] No, > > > process them as if they were part of the outer form > > > > I'm still not crazy about the whole concept, but I guess > nested forms > > can be useful sometimes. I just hope we don't open up > another can of > > worms. > > Hmmm.... breakfast. We already allow nested forms, but we > don't do anything about it, and these fail horribly at the > moment as Korbinian reminds us of constantly. The only other > option would be to check the markup and throw a runtime > exception that nesting is not allowed. > > I think the way we treat nested forms in 2.0 and 1.3 a real > improvement and a showcase for component frameworks: work > around problems in an elegant and meaningful way. Abstract > away the limitations of the protocols we have to work with. > > > My vote: > > [ x ] Yes, don't process those pesky little fields > > > > as that is more explicit/ less magic. > > Thanks for the vote. > > Martijn > > -- > <a > href="http://www.thebeststuffintheworld.com/vote_for/wicket";>Vote</a> > for <a > href="http://www.thebeststuffintheworld.com/stuff/wicket";>Wicket</a> > at the <a href="http://www.thebeststuffintheworld.com/";>Best > Stuff in the World!</a> >
