Thank you for reporting this bug. We will make it our priority to review this report.
  1. #11
    Sencha User
    Join Date
    Oct 2011
    Location
    Germany
    Posts
    50
    Vote Rating
    10
    apsq will become famous soon enough

      2  

    Default


    Yeah, the storeId doesn't really matter unless you reference it explicitly.

    The point is that the storeId on the class is used as a fallback if none is provided in the constructor call. As you can practically have multiple stores with the same storeId (though it's most likely a very bad idea), the storeId does not seem to be *really* really required by ExtJS.

    Currently what SA does when you pick a store for a view is that it will output whatever the store's storeId is in the generated code. It would be helpful if there was a way to specify it should automatically create a new instance of the class instead (ideally with an auto-generated random storeId).

    One problem remaining with that approach is that paging toolbars need an explicit store instead of inheriting the store of their container. This is most likely a shortcoming of ExtJS rather than SA, though.

    Right now, it's impossible to create views in ExtJS that have stores in them and then create multiple instances with different stores without overriding the store property in the constructor (i.e. it's impossible when this is not an option, such as on a grid nested inside a view you want to instantiate on the fly). The only way around this is overriding Ext.define and Ext.applyIf.

  2. #12
    Sencha User
    Join Date
    Mar 2008
    Posts
    51
    Vote Rating
    2
    art.dev.ext is on a distinguished road

      0  

    Default


    Hi!
    Do you (SA/ExtJs Team) consider this as a BUG ? if yes, could you please give us a #BUGID ?

    Using multiple stores with different ids but with same behaviours would be great here.

    Thanks

  3. #13
    Sencha - Architect Dev Team aconran's Avatar
    Join Date
    Mar 2007
    Posts
    9,366
    Vote Rating
    128
    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


    Quote Originally Posted by art.dev.ext View Post
    Hi!
    Do you (SA/ExtJs Team) consider this as a BUG ? if yes, could you please give us a #BUGID ?

    Using multiple stores with different ids but with same behaviours would be great here.

    Thanks
    It's definitely an issue that we are aware of and will try to address in the future.

    The problem is there are inherent problems with how MVC treats its stores that intertangle with the possible solutions we have here.
    Aaron Conran
    @aconran
    Sencha Architect Development Team

  4. #14
    Sencha User
    Join Date
    Mar 2008
    Posts
    51
    Vote Rating
    2
    art.dev.ext is on a distinguished road

      0  

    Default


    OK!
    So could you please change thread title and give us an issue n# to follow ?
    Thank you