Add support for something like EventObject in dispatchEvent method

[icaine]

I would like to use something similar to $em->dispatchEvent(new App\Events\StartupEvent(...)) instead of $em->dispatchEvent('app.startup', ...) . Because this way i dont have to remeber exact "string" name of the event and what parameters/arguments i need.

It also may be easily implemented to dispatchEvent method:

if ($eventName instanceof Kdyby\Events\EventObject) {
    $eventArgs = new EventArgsList(array($eventName));
    $eventName = get_class($eventName);
}

What do you think about it?

[fprochazka]

On the first look, I really like the idea, but I'm not sure if there aren't any non-obviouse design issues with it (with usage of the pattern).

[newPOPE]

+1

Maybe new App\Events\StartupEvent(...) is not good example, I like something like new App\Events\AppStartupEvent(...) or new PostCommentedEvent(...)...

[enumag]

I can see one problem. The EVM would hold a map like [ classname => array_of_listeners ]. Imagine you would want to add some parameters to a existing event - you would extend the event class and add some properties and methods to it. But the extended class would not work because its class name won't be in the map.

(edit) Solution: EventObjectInterface::getEventName().

[klimesf]

+1 for the idea, events can be more than just data. Great move towards OOP.
+1 for EventObjectInterface::getEventName().

[icaine]

It is on the programmer to decide whether to use objects or simple arrays. Otherwise we would still use the fastest plain PHP.. :)

[solcik]

+1

[fprochazka]

@enumag actually, EVM already considers inheritance.

[enumag]

@fprochazka I know but that's for listeners, this is different.

[foxycode]

+1

[fprochazka]

I would love to implement this, but it would be out-of-scope. #97 (comment)