I have a small patch set that I apply to the current build. The patch is very small. I began comparing Ext JS 2.3.0 and the current build. The path taken last night was simply this:
1. I pulled up the portal demo running 2.3.0 and another portal demo using the current build.
2. My focus was basically to follow the path for collapsing and expanding the west border region.
3. Immediately, I saw something during profiling. The current build had numbers double that of 2.3.0 for some function calls.
4. It's an overhead somewhere and I wanted to find it.
## Enjoy the results :)
# of calls
# of calls Max/Restore
Build (40 tabs) Time Window Size Time
======== ========== ======== =========== ========
3.0.3 477,580 5.691 399,909 9.466
3.1.0 404,538 5.829 246,995 11.327
R.5994 418,970 5.692 31,848 0.811
R.C3 402,543 5.468 5,246 0.557
<!-- Buffer resize is set to false in index.html -->
Ext.Container.prototype.bufferResize = false;
The Max/Restore Window Size combines both maximizing and restoring the window size.
The times above are in number of seconds and measured with profiling enabled.
Therefore, it's faster when not profiling.
How does the new Firefox stack up against IE 6 and 8?
Tests were done against the R.C3 build.
Resizing is nice with Firefox. Things sizes and falls into place nearly as fast as IE 8.
Browser Form Grid Editor Table
========= ======= ======= ======== =======
IE 6.0 1.125 0.625 1.609 4.125
IE 8.0 0.624 0.546 1.061 2.387
FF 3.6 0.874 0.586 1.173 1.665
I will share my R.C3 delta with the dev team. It's very small and applied to the current build.
I need to run some additional tests. So far all looks good. Also keep in mind that the current build is also nice.