tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fritz Pröbstle (JIRA) <...@tapestry.apache.org>
Subject [jira] Updated: (TAPESTRY-2520) (Select) - Event Bubbling - No chance to handle more submit buttons from the component in the container
Date Tue, 15 Jul 2008 11:19:32 GMT

     [ https://issues.apache.org/jira/browse/TAPESTRY-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Fritz Pröbstle updated TAPESTRY-2520:
-------------------------------------

    Description: 
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.



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?
 

  was:
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() .



This may be not a really bug (there are workarounds) but this workarounds may produce awksome
code.
I wouls like to have an "Event-Bubble solution " for this issue


> (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.
> 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


Mime
View raw message