1. #1
    Sencha Premium Member
    Join Date
    Jun 2013
    Location
    Boulder, CO
    Posts
    538
    Vote Rating
    7
    DavidThi808 is on a distinguished road

      0  

    Default passing additional config props to init

    passing additional config props to init


    Hi;

    I need to set things like a proxy api read uri and a TreeStore root name programatically. I believe the way to do this is by passing in additional config properties. However, I can't figure out how to do this in Architect. Is there something that explains how to do this?

    thanks - dave

  2. #2
    Sencha Premium Member
    Join Date
    Jun 2013
    Location
    Boulder, CO
    Posts
    538
    Vote Rating
    7
    DavidThi808 is on a distinguished road

      0  

    Default


    Help please.

  3. #3
    Ext JS Premium Member tangix's Avatar
    Join Date
    Mar 2010
    Location
    Stockholm, Sweden
    Posts
    550
    Vote Rating
    50
    tangix is a jewel in the rough tangix is a jewel in the rough tangix is a jewel in the rough

      0  

    Default


    Maybe this old thread can help...
    http://www.sencha.com/forum/showthread.php?263665

  4. #4
    Sencha Premium Member
    Join Date
    Jun 2013
    Location
    Boulder, CO
    Posts
    538
    Vote Rating
    7
    DavidThi808 is on a distinguished road

      0  

    Default


    Hi;

    That will work for one case - thank you.

    But for the other cases, we have windows that are called on the fly and we only know the url for the datasource at the time we call it. And it will change each time we call. Is there a way to pass in the url?

    thanks - dave

  5. #5
    Ext JS Premium Member tangix's Avatar
    Join Date
    Mar 2010
    Location
    Stockholm, Sweden
    Posts
    550
    Vote Rating
    50
    tangix is a jewel in the rough tangix is a jewel in the rough tangix is a jewel in the rough

      0  

    Default


    OK - tougher one.
    In one of my projects I am handling multiple tabs by creating individual stores for each tab (each tab has a grid and a couple of comboboxes) and then setting references to the grid in the tab to that store in the tab instance.
    I found out that I needed to be careful not to leak objects and when I close a tab I had to do a manual Ext.destroy() on the store.

    /Mattias

  6. #6
    Sencha Premium Member
    Join Date
    Jun 2013
    Location
    Boulder, CO
    Posts
    538
    Vote Rating
    7
    DavidThi808 is on a distinguished road

      0  

    Default


    Let me ask you a larger question - do you think Architect is worth it with the stuff like this you have to do?

    I'm starting to think we should create the initial window layout in Architect, then copy that over to our code base and at that point use WebStorm instead.

    ??? - thanks - dave

  7. #7
    Ext JS Premium Member tangix's Avatar
    Join Date
    Mar 2010
    Location
    Stockholm, Sweden
    Posts
    550
    Vote Rating
    50
    tangix is a jewel in the rough tangix is a jewel in the rough tangix is a jewel in the rough

      0  

    Default


    I am not sure I understand your question - having one store per tab is a neccessity imposed by the framework as the filtering from a combobox and grid are applied to one store and can't be shared among instances. This has nothing to do with Architect.

    If you ask if I think Architect is worth it unrelated to this issue, my answer will be a simple "yes!".

  8. #8
    Sencha Premium Member
    Join Date
    Jun 2013
    Location
    Boulder, CO
    Posts
    538
    Vote Rating
    7
    DavidThi808 is on a distinguished road

      0  

    Default


    Hi;

    Let me explain better. I have a Window that a user uses to create a select for a database. The window needs to call our REST server to get the metadata for that database and the name of the database is part of the URL for the Store/Model that is the data store for the tree in the Window that displays the metadata.

    So, each time this Window is created, it will have a different URL for the tree's data. Every user can have multiple databases and we have many users. So it's not even a set of 20 pre-defined URLs, it's something that does have to be defined each time the Window is instantiated.

    In addition, there can be multiple instances of this Window up at once. So each Window needs it's own instantiation of its Store because each will have a different URL.

    So I think this means that 1) The Store object must be created inside the Window object so each Window has its own Store object and 2) That we have to set the URL of each Store object when we create it.

    Did I miss something or do we need to structure the code as I listed? And if we do, then I think Architect is not usable because it makes the Store a global object and it only allows a literal URL.

    ??? - thanks - dave

  9. #9
    Sencha Premium Member
    Join Date
    Jun 2013
    Location
    Boulder, CO
    Posts
    538
    Vote Rating
    7
    DavidThi808 is on a distinguished road

      0  

    Default


    Hi all;

    Does anyone have an idea how to do this in Architect?

    thanks - dave

  10. #10
    Sencha - Architect Dev Team aconran's Avatar
    Join Date
    Mar 2007
    Posts
    9,198
    Vote Rating
    120
    aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold aconran is a splendid one to behold

      0  

    Default


    David -

    At one point (Ext Designer 1.0 days) there was an option on every bindable item that would allow you to instantiate an instance of a store. We do not currently have an option to do that, though we should bring it back. Currently you would have to make a duplicate of the existing store.
    Aaron Conran
    @aconran
    Sencha Architect Development Team

Thread Participants: 2

Turkiyenin en sevilen filmlerinin yer aldigi xnxx internet sitemiz olan ve porn sex tarzi bir site olan mobil porno izle sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli porno izle siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir. Mesela diğer sitelerimizden bahsedecek olursak, en iyi hd porno video arşivine sahip bir siteyiz. "The Best anal porn videos and slut anus, big asses movies set..." hd porno faketaxi