On 09/24/2012 01:49 AM, [email protected] wrote:
Ahh, that explains it, thanks for that. For a bit of contextI have a nested tree structure dynamically populated with selectable options pulled from config, containing checkboxes, radio boxes and custom selection widgets all of which need to trigger an event and some of which are nested within other selectable options. (Think, select an option and a different list of options are displayed, select one of those and yet more options are displayed.) I
So you were thinking of the construction hierarchy of your app widgets.
wanted to avoid having listeners in each node of my tree structure which purely catch events and re-fire them but I may just have to do that.
Well, you need to have a listener in each node of your structure anyway. As for the re-firing, a common pattern to use here would be a message bus [1]. The selected widget sends a message, and the bus dispatches it to the subscribers. All that is left is a filter logic at one end or the other, but that shouldn't be too hard (maybe you could use different messages for that).
T. [1] http://demo.qooxdoo.org/2.0.x/apiviewer/#qx.event.message.Bus
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
