1. #1
    Sencha User
    Join Date
    Oct 2011
    Posts
    127
    Answers
    4
    Vote Rating
    0
    robl is on a distinguished road

      0  

    Exclamation Unanswered: Orthogonality of Ext.app.Controller MVC accessor methods

    Unanswered: Orthogonality of Ext.app.Controller MVC accessor methods


    I'm looking at the reference documentation for Ext.app.Controller. There is a method getView(String name) but there is no method to query a controller for all it's views nor is there a way to add a view to controller or remove one. There is also no way to get the Application instance for a given controller. Why is that? The same applies for models, controllers and stores as it does views.

    I would think that Controller would have these methods (or something similar). Please explain to me why it should or should not have these methods.

    getApplication()
    Returns application associated with this controller

    getViews()
    Returns list of all views associated with this controller

    addView(Ext.base view)
    Adds a view to this controller

    removeView(Ext.base view)
    Removes a view from this controller

    getModels()
    Returns list of all models associated with this controller

    addModel(Ext.data.Model)
    Adds a model to this controller

    removeModel(Ext.data.Model)
    Removes a model from this controller

    getStores()
    Returns list of all models associated with this controller

    addStore(Ext.data.AbstractStore)
    Adds a store to this controller

    removeStore(Ext.data.AbstractStore)
    Removes a store from this controller

  2. #2
    Sencha User
    Join Date
    Oct 2011
    Location
    Vancouver, Canada
    Posts
    157
    Answers
    5
    Vote Rating
    14
    el_chief will become famous soon enough

      0  

    Default


    • this.application returns a controller's application
    • you probably want to consider one controller class per view class, though multiple view instances per controller instance

Thread Participants: 1