On 3 April 2012 20:51, Marc Abramowitz <msabr...@gmail.com> wrote: > So I think approach 1 gives you easier to understand code, but if you have > to deal with a lot of different events, you can end up with an explosion of > classes. That lead me towards approach #2 (and it looks like the Zikula > GenericEvent might've been motivated by that as well?). So my observation > then is that Zikula subclasses EventManager and Event and my code does too. > So that suggests that something like GenericEvent could be a useful class > and perhaps something like it should be included with EventDispatcher. Or > alternatively, the base Event class could be augmented with $data, > $arguments, etc. >
Just a note, Zikula is refactoring to Symfony and the EventManager is just a BC class now while we do our refactoring. The GenericEvent can just extend the Sf2 Event object and it's ready to go. I'll ask Fabien if he'd like a generic event object in the EventDispatcher, it could be a nice entry level thing for those who want. Drak -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
