Wait! Looks like we don't have enough information to add this to bug database. Please follow this template bug format.
  1. #31
    Ext JS Premium Member SebTardif's Avatar
    Join Date
    Feb 2011
    Location
    Cambridge, MA
    Posts
    299
    Vote Rating
    8
    SebTardif is on a distinguished road

      0  

    Default


    I think the thread made pretty clear how convoluted the API is.

    What have not been covered very well, is that we need a separation between the store and the view. I mean the lazy rendering should be a view concept, I don't understand why it seems most of the APIs end-up in the store.

    All lazy rendering settings should be at the view, not at the store. With the current code, I get some weird side effect, like depending of store settings I will get more not visible row renderend or less, and with this, all kind of bugs, including getting half of the visible rows rendered when scrolling.

    As long lazy rendering is not the grid default behavior, or a more realistic set of public examples exist, I don't believe we will get something without a large number of issues.

  2. #32
    Sencha - Community Support Team edspencer's Avatar
    Join Date
    Jan 2009
    Location
    Palo Alto, California
    Posts
    1,939
    Vote Rating
    7
    edspencer is a jewel in the rough edspencer is a jewel in the rough edspencer is a jewel in the rough

      0  

    Default


    I believe these are totally separated - what specifically are you referring to where they are too closely coupled?
    Ext JS Senior Software Architect
    Personal Blog: http://edspencer.net
    Twitter: http://twitter.com/edspencer
    Github: http://github.com/edspencer

  3. #33
    Ext JS Premium Member stevil's Avatar
    Join Date
    Nov 2007
    Location
    Denver, CO
    Posts
    1,045
    Vote Rating
    9
    stevil will become famous soon enough

      0  

    Default


    Quote Originally Posted by SebTardif View Post
    <snip>

    All lazy rendering settings should be at the view, not at the store. With the current code, I get some weird side effect, like depending of store settings I will get more not visible row renderend or less, and with this, all kind of bugs, including getting half of the visible rows rendered when scrolling.

    As long lazy rendering is not the grid default behavior, or a more realistic set of public examples exist, I don't believe we will get something without a large number of issues.
    I think there are two components to rendering - the rendering of the grid's chrome (panel header, column headers, borders, etc.), and rendering the data - if you're talking about the data, that should be implicitly "lazy", as the grid awaits a data result from the store and the proxy?

    Or perhaps I'm missing your point (which is a distinct possibility)?

    stevil

  4. #34
    Ext JS Premium Member SebTardif's Avatar
    Join Date
    Feb 2011
    Location
    Cambridge, MA
    Posts
    299
    Vote Rating
    8
    SebTardif is on a distinguished road

      0  

    Default


    I'm just talking about the data rendering. Ideally, no code about virtual rendering should exist in the store class. I understand to support infinite scrolling the store need extra code.

    I previously listed some strange side effect here: http://www.sencha.com/forum/showthre...ing-AJAX-proxy

    At the end of the day, the virtual rendering should not break because of a store state/config.

  5. #35
    Ext JS Premium Member stevil's Avatar
    Join Date
    Nov 2007
    Location
    Denver, CO
    Posts
    1,045
    Vote Rating
    9
    stevil will become famous soon enough

      0  

    Default


    Is it that the store is doing virtual rendering, or that, in doing buffered prefetches, it's firing off prefetch and/or load events to whatever's listening, in this case presumably the View?

    stevil

  6. #36
    Sencha - Community Support Team edspencer's Avatar
    Join Date
    Jan 2009
    Location
    Palo Alto, California
    Posts
    1,939
    Vote Rating
    7
    edspencer is a jewel in the rough edspencer is a jewel in the rough edspencer is a jewel in the rough

      0  

    Default


    The Store is not doing anything to do with rendering. That is all handled in the view layer. If you're aware of code in our framework that breaks that abstraction I'd love to see it
    Ext JS Senior Software Architect
    Personal Blog: http://edspencer.net
    Twitter: http://twitter.com/edspencer
    Github: http://github.com/edspencer

  7. #37
    Ext JS Premium Member stevil's Avatar
    Join Date
    Nov 2007
    Location
    Denver, CO
    Posts
    1,045
    Vote Rating
    9
    stevil will become famous soon enough

      0  

    Default


    I'm know that *I'm* not - I am interested to know more about what @SebTardif was experiencing...

    stevil

  8. #38
    Ext JS Premium Member SebTardif's Avatar
    Join Date
    Feb 2011
    Location
    Cambridge, MA
    Posts
    299
    Vote Rating
    8
    SebTardif is on a distinguished road

      0  

    Default


    My last post mentioned a previous thread about the strange side effect on the view via the store. That should be enough to give some pointer.

    Beside that, the following use case should also be covered: http://www.sencha.com/forum/showthre...983#post602983

    and this one -> http://www.sencha.com/forum/showthre...563#post626563

    and also this one -> http://www.sencha.com/forum/showthre...577#post630577

Similar Threads

  1. Replies: 9
    Last Post: 28 Nov 2012, 3:00 AM
  2. [FIXED] Buffered Store with infinite grid - scrolling issues
    By gctram in forum Ext:Bugs
    Replies: 14
    Last Post: 8 May 2012, 6:32 AM
  3. [OPEN-EXTJSIV-207] Mixins issues
    By LesJ in forum Ext:Bugs
    Replies: 3
    Last Post: 21 Mar 2011, 12:58 PM
  4. [OPEN-EXTJSIV-205] Numeric axis issues
    By vdan in forum Ext:Bugs
    Replies: 1
    Last Post: 20 Mar 2011, 11:21 PM
  5. Replies: 1
    Last Post: 20 Aug 2010, 10:34 PM

Thread Participants: 9