EXT 3.1 is released and can be downloaded for free.

ArticleDirectory

• Internet Explorer Memory improvements
• Optimized layouts
• Eventmanager refactor
• Improved flexibility
• New Components

You can download the following link:

Http://www.extjs.com/products/extjs/download.php? DL = extjs310 & ref = extjsgreenbutton

 

 

The main improvements to ext 3.1 include:

Original article: http://www.extjs.com/blog/2009/12/17/ext-js-3-1-massive-memory-improvements-treegrid-and-more%E2%80%A6/

 

 

Internet Explorer Memory improvements

As single-page, complex, Web apps are becoming more are more
Prevalent, memory management internal SS all browsers has become a critical
Issue. With ext JS 3.1, we have implemented a wide array of workarounds
For memory leaks-most notably in IE 6 +.

 

When single pages and complex Internet-based applications become more and more common, the cross-browser memory manager has become a crucial issue. Ext js 3.1 has greatly improved this problem, especially for IE 6 or later versions.

 

 

Dom leaks

DOM reference leaks are one of the biggest performance hits in
App. Ext JS 3.1 has undergone extensive refactoring to ensure all
Components are properly removing Dom references, in both Ext JS and ext Core
. The result has been the removal of nearly all orphan nodes when removing elements in IE (Sorry IE6/7 form tags!
).

 

Dom leakage is the biggest performance problem in Web applications. Extjs 3.1 has already done a lot of refactoring work on this issue to ensure that all components can normally Delete DOM nodes. Whether it is ext JS or ext core, when an element is deleted in IE, individual nodes under the element are cleared.

 

JScript engine leaks

Most surprising was that even simple extends cipt objects leaked, even through and including ie8.All
Current versions of IE suffer from a poor implementation of
JavaScript Object which, on long lived and often used objects such
Caches, cause large memory leaks.
IE 9 may correct this issue
In the meantime, 3.1 captures the benefits of a uniied element Cache
Workaround that is flushed during garbagecollection in IE. In certain
Tests, we gained a 50x memory playback ction for long-running single-page
Apps.

 

The most surprising thing is that even a simple javascipt object may leak, which may even happen on ie8. Currently, all Internet Explorer versions
The poor use of JavaScript objects leads to a large amount of memory leakage, such as a short life cycle and frequent use of cached objects. Ie9 can solve this problem, at the same time, in ext
JS 3.1 captures the advantages of a uniform element cache area and performs write-erase during garbage collection in IE. In some tests, the memory usage for a long running single page is reduced by 50 times.

Optimized layouts

In 3.0 parse components were changed to become containers
To allow for complex dynamic interfaces. In version 3.1, we have gone
Back to optimize this process, removing redundant callto expensive
Layout calculations wherever possible. We also now suspend resizing
Child containers until the layout process is complete which prevents
"Layout Storm" which cocould occur previusly. In 3.1, destroying
Component also removes the component from it's iner, greatly
Improving Performance and optimizing other functions that were being
Executed.

 

In version 3.0, many components have been modified to container class objects to implement more complex dynamic interfaces. This process has been optimized in version 3.1, removing redundant callbacks to reduce time-consuming layout computing. Currently, the size of the sub-container is not adjusted during the layout process. The sub-container is processed only after the layout is completed, which avoids the "layout Storm. In version 3.1, deleting a component will be deleted with its container component, which greatly improves performance and optimizes processing functions.

Eventmanager refactor

The eventmanager
And underlying core adapter have undergone a full refactor to remove
Code duplication and inefficiency. The previous event caching mechanic
Was overhauled to provide a faster and more consistent experience.
Complex containers, this can result in an order of magn?improved
Response time. buffered and deferred events are now being removed
During element and component destruction stopping extraneous events
From being executed.

 

Note:
Eventmanager and core adapters are all restructured to remove duplicates and inefficientCode. Previously, the event caching mechanism has been fully adjusted to provide a faster and more consistent experience. For example, the response time of a complex container is greatly improved. When an element or component is deleted, buffering and bubbling events are blocked.

Improved flexibility

When ext Core
Was moved to its own repository in 3.0
, There were implements private methods which made core difficult to extend. The ext community
Asked for greater flexibility and we have delivered in 3.1, with most methods becoming open prototypes.Ext. Each
Was also unrolled from much of the internal codebase, resulting in better performance on every common tasks.

 

In ext core 3.0, many core libraries are difficult to expand because of their core libraries. To solve this problem, extCommunityThe requirement is more flexible, and in version 3.1, we have implemented this requirement to make version 3.1 the most open prototype method. Ext. Each should also be enabled from the internal code library to improve the performance.

New Components

While the performance improvements in 3.1 are drastic, we love
Releasing our latest visual creations. Here are some of our most
Requested components and enhancements which are being encoded
Defaults with 3.1:

While improving performance, Version 3.1 also adds many new components. For example:

New treegrid Extension

Our new treegrid component
Creates the perfect hybrid for lists-combining the power of a grid
(Sorting, showing additional information) with the flexibility and UI
Of a tree. (MS Project). treegrid is currently based off of treepanel,
For code optimization and performance. We are also currently working on
Creating a treestore which will support hierarchical data structures,
Which will appear in 3.2. This has been one of our biggest component
Requests which we're re now happy to deliver:

 

The new treegrid component allows you to create a more perfect list display, which is composed of a powerful and flexible grid (sorted and display additional information) and a tree interface. Treegrod's base class was treepanel at that time, and the code was optimized to improve performance. We are currently creating a treestore to support hierarchical data structures, which may appear in version 3.2.This has always been our biggest component requirement, and we are happy to implement one of them:

 

 

Locking grid Columns

Locking grids columns return with the new lockinggidview/lockingcolumnmodel
UX, allowing users to view specific columns while scrolling horizontally.

 

 

The lockinggidview/lockingcolumnmode object can be used to lock the grid columns, so that users can view specific columns through the vertical scroll bar.

 

Grid column grouping plugin

With the new columnheadergroup plugin
, Grid columns can now be grouped together easily. columns can also be reordered within a group, for maximum flexibility.

 

The new columnheadergroup plug-in allows you to easily group titles. The column can also beYou can rearrange a group to maximize flexibility.

 

Summary

With 3.1 we took a deep look into optimizing into algorithms
Improve ie support, overall performance, and introducing new
Functionality. We think these enhancements will greatly improve your
User's productivity while supporting faster, more robust applications.
We are also still hard at work on the ext designer
, Which we hope to debut in the next few months. Make sure to update your version
Today and check out the new features for yourself.