Don't do this; it breaks modularity. The FilteredNoteCollection class is used elsewhere and should know nothing about the omnibox.

Unfortunately, the filtered note collection doesn't have attributes. If you want, you can wrap it in a module but that is probably overkill. Instead, I would just set a status attribute (probably a tristate to indicate success, failure, and searching) on the the FilteredNoteCollection instance itself and then trigger a `search:fail` event in place of the `search:complete` event. This is sufficient because it also triggers a `search:begin` event. The omnibox would then listen to these events and set it's state appropriately. The status attribute probably isn't necessary but makes it easier to determine the collection's state.