1. #11
    Touch Premium Member BostonMerlin's Avatar
    Join Date
    Aug 2010
    Location
    Boston
    Posts
    497
    Vote Rating
    41
    BostonMerlin has a spectacular aura about BostonMerlin has a spectacular aura about BostonMerlin has a spectacular aura about

      0  

    Default


    you're welcome. just "paying it forward".

  2. #12
    Sencha User
    Join Date
    Nov 2012
    Location
    Mauritius
    Posts
    43
    Vote Rating
    3
    Shabneez is on a distinguished road

      0  

    Default


    thank you thank you thank you! now i understand it much much much better

  3. #13
    Sencha User
    Join Date
    Nov 2012
    Location
    Mauritius
    Posts
    43
    Vote Rating
    3
    Shabneez is on a distinguished road

      0  

    Default


    thank you, now I understand

  4. #14
    Sencha User
    Join Date
    Jan 2013
    Location
    Ca
    Posts
    13
    Vote Rating
    0
    DNRDustin is on a distinguished road

      0  

    Default


    Quote Originally Posted by BostonMerlin View Post
    Typically, you'll create a view then add it to the (viewport or another view) at the time it's needed. you might, for performance reasons, create a view before it needs to be shown but you'll need to be cognizant of the limited memory constraints of the device the app is running on.

    to keep things simple, create your view based on the action of some other event (i.e. login button -> authenticate -> hide/destroy login view -> show main view).

    Link / move / copy are architect-only commands. "Link" is another way of saying visual inheritance. I want to create a new view (A) based on another view (. A will get everything B has and let me change things around on the A view w/out changing the B view. Read up on OOP inheritance to get the bigger picture

    Much of what you're asking is detailed in the many online documents and tutorials provided by Sencha.

    Architect Docs - Reusing components.
    http://docs.sencha.com/architect/2/#...ing_components

    Hope that helps
    John
    I on the other hand am lost on this. Also, that link is dead. Maybe someone can explain this to me. With Touch it would go something like
    //add as many top level or child views as you want and call them with itemId, userAlias, or //userClassName

    Ext.define('MyApp.controller.Login', {
    extend: 'Ext.app.Controller',


    config: {
    refs: {
    loginView: 'loginPnl'
    },


    control: {
    "button#loginBtn": {
    tap: 'onLoginBtnTap'
    }
    }
    },


    onLoginBtnTap: function(button, e, eOpts) {
    var loginView = this.getLoginView();
    console.log(loginView);


    Ext.Viewport.setActiveItem(Ext.create('MyApp.view.MyView'));
    Ext.Viewport.remove(loginView);
    }
    });
    So I either want to have top level views linked to a Viewport, or just have them as children of it. Every tutorial of gone through seems to stop right before implementing the actual controller action.
    All I want to do is mimic the above sencha code in extjs to go from one "view" to another. clickBtn Somewhere --> go somewhere else(show/focus/remove/destroy/etc.. something else).
    A code snippet would be much appreciated, and thanks in advance.

film izle

hd film izle

film sitesi

takipci kazanma sitesi

takipci kazanma sitesi

güzel olan herşey

takipci alma sitesi

komik eğlenceli videolar