Forums

Hi,
Im having a design problem when using bubbling library to install listeners. First I will provide my perspective of the bubbling library, then my usecase and my design solution. The problem is the solution as you will see involve moving away from the bubbling library. I want to have that as a last resort. So I will be happy if you could help me redesign my usecase so that i can use the bubbling library.

1. Perspective of Bubbling library (When your view about something is wrong, the solution is wrong 100 % )

1. The YUI Bubbling library installs listeners only to the Body element of the document.

Disadvantages,

consider,

<div class="list">
<input type="button" class="AsyncRequestTrigger">
</div>
<div class="editable list">
<input type="button" class="AsyncRequestTrigger">
</div>

The problem(usecase) is i want to handle the AsyncRequestTrigger in the two divs differently. One Solution is checking for an ancestor(of the target) with a particular class - this is not an elegant solution. Not elegant because it becomes the responsibility of the element to check whether it is the actual trigger or not.

So my solution is to consider each of the div as a separate behavior layer(there by it has listeners attached to it). So that each class under a different behavior layer can behave differently.

Question 1). Is it possible using the bubbling library?

Question 2). If so can you design it out for me?

Many regards,
Jiraaya - "To heaven be the glory"

@ Caridy

Thank you for the much needed information. Unfortunately, due to life cycle constraints, I had to extend your bubbling library to provide support for multiple behavior layers. Will take consider your solution of using delegate the next prototype comes up. Thank you once again

PS: Late knowledge is still knowledge