> Date: Tue, 13 Nov 2012 09:03:18 -0600 > From: matt...@zend.com > To: fw-general@lists.zend.com > Subject: Re: [fw-general] Events vs. EventManager > > -- Andreas Möller <a...@softe.is> wrote > (on Tuesday, 13 November 2012, 03:48 PM +0100): > > > If you're talking about the _protected_ property, or the fact that many > > > setEventManager() implementations use "$events" as the name of the > > > EventManager property, or even that many examples will use constructs > > > like "$events = $object->getEventManager();" it's simply because: > > > > > > a) it's shorter to type > > > b) it has a semantic affinity to how other languages (esp. JavaScript) > > > refer to event collections/managers. > > > > But it doesn't reveal what it really is - it is not a list of events, > > it's an instance of EventManager . . . ! > > > > Why is the EventManager class then named EventManager, not Events? > > It aggregates listeners and triggers events; it could have been named > either way, to be honest. "EventManager" is cumbersome as a variable > name, but perfectly fine as a class name. > > > > In JavaScript, you typically work with an "events" collection, and > > > attach/trigger from that; we chose terminology that should be familiar > > > to those familiar with that paradigm (which will be a majority of web > > > developers). > > > > Still, it's an event manager. > > Honestly, I've never heard anybody else complain about it. At this > point, I'm not about to change all occurrences of it, either. > > > -- > Matthew Weier O'Phinney > Project Lead | matt...@zend.com > Zend Framework | http://framework.zend.com/ > PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc > > -- > List: fw-general@lists.zend.com > Info: http://framework.zend.com/archives > Unsubscribe: fw-general-unsubscr...@lists.zend.com > >
I agree with some of his points. You haven't heard me complain because I've stopped caring about these kind of things. I don't advocate changing these things at this stage either. zf3 is the place for that. -- Gerard