No, I understand that lib/camera.js is supposed to ultimately be a reusable camera abstraction. I still think though that instead of having a controller listen for `camera:configured` on the `app` object, couldn't it just listen directly for the `configured` event on `app.camera`? I guess it does make more sense to "broadcast" these as global app events, but I'm not sure it has anything to do with keeping lib/camera.js app agnostic. I just thought I'd bring up some discussion on it, but I'm not sure that its hurting performance in any noticeable amount so it doesn't really matter I guess. If anything, some of the call stacks might be a little deeper.