Heh, I get your explanation! It depends. If it broadcasted only a generic "hey, the window size changed, everyone do whatever you want in response to that" event, then this function would fit better here. But it already takes an action that is specific to the Dashboard/Graph controller (broadcasting a `redrawGraphs` event), which exposes too many internal implementation details to the root scope.

So either we just fire a general "the window has resized" event here and react to that in the Graph or Dashboard controller (and then do the right things) or I think it's also ok for the lower-level controllers to hook directly into `$window.onresize` directly, since that's basically equivalent to the former, with less code.