Hi,
I havent looked into this deeply...but wouldnt you be able to
accomplish the same thing via a decorator? I know right now we do
not provide a way to decorate components, but isnt the idea of a
behavior the same as a decorator for the component
hmm, the idea is similar, behaviour (you could also call this
component plugin) would be "in the component" while a decorator would
be "around the component". I think you can roughly express the same
thing with both approaches. But I think the plugin idea (having
behaviours in a list and "forwarding" events to them) is better because:
- it gives the component a chance to interact with behaviours
- behaviours can interact together in a more transparent way, a list
of behaviours is easier to handle in these cases as the deriving
information
- behaviours could be added/removed dynamically at runtime a lot
easier; a thing you cannot do with decorators without creating new
component instances
Regards,
Ralf
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
