Changes between Initial Version and Version 1 of Ticket #10764


Ignore:
Timestamp:
Feb 22, 2010, 11:27:57 AM (12 years ago)
Author:
bill
Comment:

It turns out that Tree.postCreate() calls this._load() and does other loading-related execution. I guess I should change Tree to defer that operation until the first resize() call, but only if there's a parent widget with isLayoutContainer defined.

Need to keep the old behavior otherwise; we can't move the loading code to startup() since existing apps may not even be calling Tree.startup().

I want to give this a little more thought, because I'm a little wary of deferring loading until a widget is made visible, because there are a lot of widgets where the equivalent change could be made (FilteringSelect, !Grid, etc.), so it seems like a big decision.

I assume that in your actual application you are using a client-server store rather than ItemFileReadStore?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10764

    • Property Version changed from 0.4.1 to 1.4.0
  • Ticket #10764 – Description

    initial v1  
    33A tree in an AccordionPane that is not yet focused will call fetch() from its store and render itself. I would like to defer this behavior until the pane is focused. It makes sense as the data is not yet used, it shouldn't be requested until needed.
    44
     5{{{
    56<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
    67<head>
     
    3637</body>
    3738</html>
    38 
     39}}}
    3940Our discussion can be read here:
    4041