[KULRICE-13147] Inefficiencies in view lifecycle and rendering Created: 25/Aug/14 Updated: 24/Sep/14 Resolved: 08/Sep/14
|Project:||Kuali Rice Development|
|Component/s:||Development, User Experience (UX)|
|Security Level:||Public (Public: Anyone can view)|
|Reporter:||Jerry Neal (Inactive)||Assignee:||Jerry Neal (Inactive)|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Sprint:||UXI 2.5.0-m7 Sprint 1|
|KAI Review Status:||Not Required|
|KTI Review Status:||Not Required|
|Code Review Status:||Not Required|
|Include in Release Notes?:||
There are a few places in the view lifecycle where we are doing more than we need to which impacts performance.
The first is we rebuild the dialogs groups for each page change, even though they are only rendered on full view refreshes.
The second is we render the top group, breadcrumbs, and view header on twice on full view loads (update logic in pageGroup.ftl). On a full view refresh we don't need to render the updates in pageGroup.ftl.