Ticket #2529449 (accepted enhancement)
Reporter  Greg Hinch |
Opened: 10/18/10 Last modified: 09/19/12 Status: accepted Type: enhancement |
Owner  Satyen Desai |
Target Release: BACKLOG Priority: P3 (normal) |
|---|---|---|---|
| Summary: | Queue children rendering in WidgetParent | ||
| Description: | It would be great to be able to configure WidgetParent to render its children via a queue. Could probably work similar to the Chain class in YUI2 DataTable, allowing definition of a renderLoop size, |
||
| Type: | enhancement | Observed in Version: | 3.2.0 |
| Component: | Widget | Severity: | S3 (normal) |
| Assigned To: | Satyen Desai | Target Release: | BACKLOG |
| Location: | Priority: | P3 (normal) | |
| Tags: | Relates To: | ||
| Browsers: | N/A | ||
| URL: | |||
| Test Information: | |||
Change History
|
Posted: 10/21/10
|
|
Posted: 11/17/10
additionally, ability to call one, some, or all children's destroy() method would be good to add, to allow for properly removing children via the destructor phase rather than just removing their boundingBox from the DOM |
|
Posted: 09/19/12
Moving from 3.NEXT to BACKLOG. |
I think we need to look at performance in general for WidgetParent/Child set ups. This would include rendering to a buffer/off document, async render and lazyRender. We also need to look at lazy instantiation of Children, and also a flyweight pattern - where we could share 1 instance of a Child widget, across multiple children (like Node/NodeList, or DD Delegate).