[jira] Commented: (TAPESTRY-2520) (Select) - Event Bubbling - No chance to handle more submit buttons from the component in the container

["Robert Zeigler (JIRA)" <de...@tapestry.apache.org>]

    [ https://issues.apache.org/jira/browse/TAPESTRY-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614960#action_12614960 ] 

Robert Zeigler commented on TAPESTRY-2520:
------------------------------------------

Your component should handle the events and trigger a new event.

So you would have:

onSelectedFromAdd

and

onSelectedFromRemove

within your component's java class.

In each of those methods, then, you would trigger a new event (along the lines of resources.triggerEvent(...)).

You can then trigger an "add" event and a "remove" event, and now your page will do:
onAddFromComponent
or
onRemoveFromComponent

Now your public event contract nicely hides the implementation details of the component., and you still get the "event bubbling" that you were looking for.

> (Select) - Event Bubbling - No chance to handle more submit buttons from the component in the container
> -------------------------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-2520
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2520
>             Project: Tapestry
>          Issue Type: Bug
>    Affects Versions: 5.0.13
>            Reporter: Fritz Pröbstle
>
> I have an address component addcomp.tml with has 2 submit buttons with  t:id="add" and t:id"remove".
> I add this component (with t:id=" addcomp" ) to my Page address.tml .
> Now the page should handle the following events (pseude code)
> @Event(component=" addcomp.add")  onSelectedFromAdd() and 
> @Event(component=" addcomp.remove")   onSelectedFromRemove() .
> But the tap5 gives me only the change to hande 
> @Event(component=" addcomp")  onSelectedFromAddcomp ()
> in the page(container) code -I can get chance to handle the add and remove event individually.
> My Proposual:
> Allow something like:
> @Event(component=" addcomp.add")  onSelectedFromAddcomp_Add() and 
> @Event(component=" addcomp.remove")   onSelectedFrom Addcomp_Remove() .
> With this approach you have to know internalsof components(the Is's)- but this is a documentation issue.
> You just have to state "this component produces "add" and "remove" select-events".
> This may be done by @Annotations to have a formal documentatuion of these generated events.
> These may be used (to generate code) to call the appropriate callback-functions in the containers.
> Another solution may be to allow to alloe the sumit component to specify the Event Type generated.
> These different Evnttypes may afterwards be handlet by the container.
> This may be not a really bug (there are workarounds) but this workarounds may produce awksome code.
> I would like to have an "Event-Bubble solution " for this issue.
> But I may be wrong...
> Can you tell me how to solve my problem?
>  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org