Hi Jens and others,
I'll vote for it.
I saw your thread a few days ago ("RE: components and events + ComponentAction
+ FormSupport") and I've created 3 new JumpStart examples to try and capture
one of the techniques described. Could you please run your eye over them and
let me know if I've missed anything?
They're called "Sub-Form Component", "Sub-Form Validation", and "Sub-Form As a
Field" in http://jumpstart.doublenegative.com.au/jumpstart/
Cheers,
Geoff
On 30/08/2011, at 11:47 PM, Jens Breitenstein wrote:
> Hi Geoff, hi Wulf, hi All!
>
>
> Am 30.08.11 14:52, schrieb Geoff Callender:
>> Hi all,
>>
>> The whole business of writing and storing ComponentActions does my head in -
>> it's plumbing, and for the most part Tapestry is very good at hiding
>> plumbing, but not when it comes to input components.
> I agree...it's ugly, serialization of action classes in base64 can't be "the"
> solution
>> It seems that the source of the problem is that events bubble up from Form,
>> not down. Of course, that shouldn't change. But what if, behind the scenes,
>> something like FormSupport could trigger events in each component within the
>> Form? Maybe then we would only have to implement event handlers like these:
>>
>> onPrepareForSubmissionFromFormSupport() {..}
>> onProcessSubmissionFromFormSupport() {..}
> sounds precisely like a problem I had several days ago which results in:
>
> https://issues.apache.org/jira/browse/TAP5-1618
>
> so just vote for it and hopefully the T5 wizzards find a solution :-) ?
>
>
> Jens
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
