Improved UI performance (javascript related)
| Engineer: | Martin |
| Work remaining: | 10 days |
| QA effort | 3 days |
| No. of automated tests | ? |
Description
- Improve the performance related to legacy and ExtJS javascript include files.
- Design and implement a better revision system for javascript files so that user does not have to clear their browser cache when javascript libraries are updated.
User stories
Related Bugs
- bug-5292 Slow performance on test2 using firefox browser
- bug-5317 ExtJS-related CSS errors in FF Error Console (Was tested and the errors of the console can not be deleted because the extJS stop working fine)
Analysis & Design
In a Skype discussion with Roger, Avinash, Carlos and Alejandro. We came up with some possible solutions in order to see if we can solve the performance issue on test2. The main problem is in Firefox that takes 5 seconds to load every page (without firebug) and in IE it takes 1 second, So what we wanted to do is to take those seconds down like to 2 seconds or similiar to IE browser.
1. Use the smaller js file from the extjs (I will reduce the extjs file with the link from the extJS) Can not be done, it does not reduce anything significant for the gain that we have, and also it has some problem while creating the ext.js file
2. Compress all the js files and css from application when we make the deploy. (DONE IT)
3. Delete all the extJS files duplicated js imported --- Is already commited into the trunk. (DONE IT)
4. Refactor the js files --- We wanted to avoid js files with only one function inside. I will decouple all these files in order to avoid including too much js files in the jsp pages. (DONE IT)
5. Delete all the js files duplicated (window_functions.js and util.js)
6. Versioning of the js files. --- Avinash suggestion's is to append the version number as request parameter and not renaming the file itself.. like.../src/pnet-ext.js?v=8.3.3 (DONE IT)
