[KULRICE-9774] Review template logic Created: 14/Jun/13 Updated: 16/Jan/15
|Project:||Kuali Rice Development|
|Component/s:||Development, User Experience (UX)|
|Security Level:||Public (Public: Anyone can view)|
|Reporter:||Jerry Neal (Inactive)||Assignee:||Unassigned|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|KAI Review Status:||Not Required|
|KTI Review Status:||Not Required|
|Code Review Status:||Not Required|
|Include in Release Notes?:||
Review all FTL templates to see what logic can be pulled out of the template and moved into code. Any statements (if, loop, etc.) are much more expensive to do in templates as opposed to code.
Also, look into removing compression calls except for the one around the entire render. These are really expensive.
|Comment by Mark Fyffe (Inactive) [ 14/Sep/13 ]|
Based on analysis of which templates had the biggest footprint, the following were converted from FreeMarker template code to inline Java code:
Further review and optimization of FreeMarker template logic, if needed, will be simplified by the inline template processing feature.