// The name of controller and view does not necessary to have any relationship,
// Essentially the controller does not bind to any "view", rather than bind to
// certain UI element defined in refs, by using componentSelector
// So the MVC behavor of sencha is not exactly same as in ROR, which the name
// of controller and view has kind of mapping by default
// And the most important thing here, is that:
// WE ACTUALLY COULD BIND A DOM EVENT OF SINGLE VIEW TO MULTIPLE CONTROLLERS,
// BY DEFINE THE SAME SELECTOR!
// VICE VERSA, A SINGLE CONTROLLER COULD DEFINE SET OF HANDLERS FOR DOM EVENT
// SITS IN MULTIPLE VIEWS!