Ext JS 4.1 Update
Tweet
In August, we did a preview blog on Ext JS 4.1. In it, we explained that we were going to concentrate on Performance and Documentation for our release. We also said that we expected to ship it in “mid-to-late September”. To our disappointment, we haven’t been able to make that date, and now I wanted to update you on our new product delivery schedule.
Update: Ext JS 4.0.7 is now available Download Ext JS 4.0.7
The Challenge: Ext JS 4.0 Performance in IE7/8
Our goal for Ext JS 4.1 is to meaningfully accelerate performance on older IE browsers. Compared to IE9, Chrome and other modern browsers, IE 7 and IE8 have slow JavaScript engines and DOM interactions. Ext JS 4.0 exercises these functions particularly hard. As a result while Ext JS 4 performance is solid on modern browsers, its page display time for complex layouts is quite slow in IE7 and IE8.
Optimization Sources for IE
The Ext JS 4.1 release is focused on speeding up page display time in IE7/8. Based on initial performance profiling, we ascertained that moving from incremental rendering to batch rendering would greatly speed up page display time. We initially scoped this as a two month project. However, moving to batched rendering proved to be only half the battle. We subsequently uncovered another set of performance bottlenecks in post-rendering in IE7/8 which has taken us time to re-engineer. As a result, while we’re finally code-complete on the core refactoring, we now need stabilization and beta time. Because of this, we now expect to see a beta of 4.1 at the end of October, which we anticipate will deliver a significant speed-up in complex layouts. (Due to the similarity of IE6 with IE7/8, IE6 performance will also improve significantly). We have good confidence in our ability to hit this new date – although unexpected issues may still arise.
Releasing 4.0.7 to General Community
We’re disappointed about not being able to bring you 4.1 in the time frame we promised. As a result, we will be making our 4.0.7 release – normally only available to commercial support subscribers – available to the entire community in the next week. 4.0.7 contains almost two hundred bug releases subsequent to 4.0.2a, and we want you to have them on an accelerated time-table.
We’ll be making periodic progress reports on 4.1 on the forums as we approach final release, and providing performance workarounds in the short-term for those of you who can’t wait for 4.1 to release.
Performance Data from Complex Layouts
If you are currently encountering performance problems with your Ext JS 4.0 app on IE7/8, we’re also making a performance profiler available with instructions on how to send us performance data. We’ve identified additional areas we want to optimize for 4.2, and we’d like to gather more test data from as many applications with complex layouts as possible.
Changing How We Communicate Release Dates and Status
As we look over our ability to predict release dates, we just haven’t done a good job at this in 2011. Ext JS 4 was later than we originally announced, and our other releases have slipped past their initial launch targets. While I could take refuge in the statement “software is hard and unpredictable”, I don’t think excuses are much use to you when you have projects with hard dependencies on our ability to deliver on time. Apologies.
As a result, starting today, we’re going to be more conservative about communicating dates and we will be careful to communicate our level of confidence in those dates. In addition, we want to start providing more detail on what we’re working on and what we’re not. Using blog posts and forum posts seems to be insufficient. So, we’re looking at better ways of sharing what we’re doing with you on a continuous and transparent basis, including potentially providing open read-only access to our bug tracker.
We’re committed to Ext JS as the best application framework for desktop applications, and we hope that you’ll be pleased with our work in Ext JS 4.1.

There are 66 responses. Add yours.
Alexander Hartmaier
5 months agoThanks for keeping us updated!
slemmon
5 months agoThx for the updates. I saw some rumblings regarding Grid overhaulling in 4.1. Do you know if that is on the fix list for 4.07 or 4.1? Vertical scrollbar in IE/FF specifically is of interest, but seems there may have been a collection of fixes coming.
Thx again.
Conor
5 months agoThanks for the update guys. Really hope the calendar component makes it into v4.1 Any word on this?
Steffen Hiller
5 months agoThanks a lot for the update!
You need to dedicate a team that figures out how to remove IE 6-9 from our lives.
Shame it keeps slowing down evolution.
Les
5 months ago>> As a result, starting today, we’re going to be more conservative about communicating dates and we will be careful to communicate our level of confidence in those dates
Good idea and thank you for the update!
OnCourse Systems
5 months agoThank you for focusing on IE7/8… unfortunately there a lot of government and corporations that are still running that slop. We were unable to even look at upgrading our application to 4.0 due to how slow it ran in the older browsers.
Wemerson Januario
5 months agoThanks for keeping us updated! Have a good Job guys!
Bill
5 months agoAny word on whether the PivotGrid component will still make it into 4.1?
Daniel
5 months agoKeep the updates coming. ExtJS is a major component of our product development.
TigrouMeow
5 months agoThanks guys. I’m personally looking forward to the Neptune Theme and a stable version of the Tools SDK (for Windows). That would be cool, because right now, I’m not sure how to release my applications in a production environment in a very neat manner, and I wonder if I should rely on those tools or if I should work on some other solution by myself.
David
5 months agowhere is 4.0.7?the version in download page is 4.0.6
AwesomeBob
5 months agoDo you have a full work week? This just doesn’t make sense how such specific problems can take so long. Do you need to hire more engineers? Did everyone just stop working on Neptune? Please stick to the blogs for the updates. I check the RSS feed regularly and was glad to see more frequency this week in posts. Still the continuing trends this year makes me wonder what are the real causes of these delays. I would have figured you could get a single designer to get Neptune done in about a week or at most two but it’s been MONTHS. ExtJS 4 is already fast, but you seem to keep letting perfection get in the way of pretty damn good.
dd
5 months agoIt’s unfortunate. There is a sense that the whole product has sort of stalled/crashed out of existence somehow. Echoing AwesomeBob “Is it really that hard?”. I’d have expected hundreds or even thousands of minor fixes and new features from a full development team over six months. That it has taken so long to deliver the new theme does not give confidence that it will be easily skinned when the new theme-able version eventually arrives. Still, the focus on polish and continuing to polish is commendable - it’s just that I’m keen to see results.
Michael Mullany Sencha Employee
5 months agodd - We’ve fixed several hundred bugs since we’ve released 4.0 back in April, and have had six patch releases so far (we’re up to 4.0.6). We’ve also shipped Sencha Touch Charts.
@awesome - As far as Neptune goes. The Neptune theme shown at last year’s SenchaCON was a prototype. We understand that people really liked the way it looked. But the difficulty of designing a theme that works consistently in the very complex layouts that many of you create is non-trivial. And the initial Neptune theme could not be easily adapted to complex nested layouts. A new theme was de-prioritized for the last several patch releases as we fixed bugs that were higher priority. We’re working on it again, but I don’t want to raise expectations as to ship date just yet.
Michael Mullany Sencha Employee
5 months agoTo the other commenters: Pivotgrid will not be in 4.1 but there are a bunch of grid fixes and performance improvements.
terrycursh
5 months agoIt is so upset to hear this news. While with the GPL version is still 4.0.2a.
I have made a open source project with 4. And this Troubled me for two months.
Maybe you have forgotton the sprite of the OPEN SOURCE. SHare and SHare.
AS an OSP,I feel shame of you~
MrSparks
5 months ago@Michael Mullany
Well done guys and thanks for the update :o)
Do you anticipate that the performance refactoring will improve framework speed across all browsers or will the performance gains be limited to IE 7/8?
With that in mind do you expect 4.1 to be at least as fast as 3.x across all browsers?
Luke
5 months ago@terrycursh - I do slightly agree to some of this, as an open source framework, allowing community to develop and submit fixes in the source would be great for productivity. It takes less time to check the code and run a few tests than, figure out what you need to do, write the code, test it, write the code, test it and test it again. Why not open up your bug tracker and allow fixes to be submitted?
Burak
4 months agoWhere is the GXT 4.0 ??
Did u forget GXT :D
Thomas
4 months agoThanks for the Update!
but apart from the delayed releasedate and the focus on performace-tuning there hasn´t been much information on what to expect in 4.1…
Will the calendar components find their way back into 4.1?
Will there be tristate trees? That has been announced earlier for 4.1
Bee
4 months agoThanks Michael for update. As Extjs 4.1 may take time to release, any chances of EXTJS 4.0.7 open for everyone ?As per my knowledge higher version from extjs4.0.2a is valid/accessible for subscribers only. what about others ?
Ed Spencer Sencha Employee
4 months ago@MrSparks many of the performance improvements speed up all browsers, even the ones that were fast already. We’re optimizing first for IE8 and IE6 though
Thomas
4 months ago@Bee: Read the full blogpost:
##########################
Releasing 4.0.7 to General Community
We’re disappointed about not being able to bring you 4.1 in the time frame we promised. As a result, we will be making our 4.0.7 release – normally only available to commercial support subscribers – available to the entire community in the next week. 4.0.7 contains almost two hundred bug releases subsequent to 4.0.2a, and we want you to have them on an accelerated time-table.
Klaus
4 months agoRoadmap: It would be nice if your statements regarding future roadmaps and release dates also include statements regarding Ext GWT 3.0. Because there are so obviously similar delays.
Gevik
4 months ago@Michael
It would be great for commercial/OEM customers to gain read-only access to the development branch (git). The SVN tracking system at support.sencha.com does not reflect the latest/nightly development snapshot. Next to that, the SVN logs are pretty useless, since it only reflects a small part of your git repository. The reason for this request in mainly to anticipate the upcoming changes and being able to follow the fixes.
I understand that Sencha would be hesitant about opening access, but think about how much you can help your commercial and OEM customers with this.
Worldwide
4 months agoShame about 4.1, but thanks to you guys for pushing 4.07 to general release earlier, keep up the good work.
Luke
4 months ago@Gevik
I think opening access would be beneficial to Sencha in the fact that if people see there is a bug currently open, and they already have a fix from their development or development team, they could supply Sencha the fix speeding up bug fixing
Michael
4 months agoGuys, what we don’t need right now is a new theme and a calendar gizmo.
What we DO need is a core set of features that are stable and perform well in a variety of browsers, including especially nested layouts and grids.
Thank you Sencha for staying focused on the things that are important and tabling some of the things that aren’t until the next release.
max
4 months agoThanks Ed, Thanks Michael. I’m very excited for version 4.0.7 as I’m currently working on 4.0.2a and look forward to improvements in 4.0.7 for our internal government application.
Paul J. Taylor
4 months agoIs there any word on Adobe Air compatibility for 4.1?
Austin
4 months agoFinally with update. I’ve been waiting for an update for a while and glad to hear that 4.1 is on the way.
However, it would have been better what some of people saying about releasing new versions with slall fixes more often and allow Ext communities contribute bug fixes.
It is so shame that a such nice tool has so many bugs for simple HTML functionality that slowing down our productivity. Hope for the best with whatever we got.
John
4 months agoIt was also expected that EXT JS team would provide an RTL solution, this had been postponed many times.
When could we expect RTL version ?
thx,
John
Ed Spencer Sencha Employee
4 months ago@John RTL is top of our list of new features and is already largely implemented. We just decided to split this release so that we could ship the 4.1 performance improvements faster. However, we have not committed to a release date for RTL yet.
Gian Marco
4 months agoYou really should commit to time-boxed releases (for example, a new release every month or so). Many projects today are switching to this way of working (Chrome, Firefox, Selenium, ...)
Ben
4 months ago@Gian
Sencha already does this if you have a support subscription.
Gian Marco
4 months ago@Ben
glad to know it, but i think that by doing OSS this way, Sencha is loosing all benefits of OSS.
Right now i consider ExtJS a closed source project with open source snapshot released sometime, that you can use as is for your OSS project, and that you are not welcome to contribute back.
Ariel
4 months agoGreat news!
Any chance to have MVC localization working also?
have you scheduled a patch?
thanks for your work!
Ariel
Patrick Scanlon
4 months agoWe have been waiting for quite a long time for 4.1 We have a very large application that is using both tab panels and grids. When switching from one tab to another, it can take as much time as 30 seconds. The grids are using infinite scrolling with a page size of 200, and the largest grid has around 20 columns. The scrollers randomly will invalidate and disappear, or they will be there, THEY will scroll up and down, but the grid does not. Almost 90% of our development time has been spent trying to remedy Ext 4. This has been an extremely frustrating pursuit to build a web application. It is a great app for tiny little widget web apps, but I would think more than twice to use it at an enterprise level. I am frustrated now because I can no longer access the SVN. Can someone please contact me from SENCHA? Can we get in the 4.1 beta. This project is VERY important and we have been promised 4.1 for a very long time now. DO SOMETHING. Thanks.
Joeri Sebrechts
4 months agoThanks for communicating. I feel that the big issue with 4.x has always been communication, not progress. Sencha develops new stuff fast enough, but they should manage expectations better. Maybe 4.0 should have been presented as experimental, with the 3.x line recommended for projects until 4.x had time to stabilize. Currently I’m still on 3.4, and I must say that it works just fine for production apps, even on older versions of IE.
Brian Polk
4 months agoHi, all. Great product. Been an enthusiastic developer using Ext since 2.0. I echo the others in anticipation of 4.1, but I agree that it would be better to explain delays to my customers than to explain an unexpected amount of defects.
For now, I have been checking back hoping to find the 4.0.7 release like 2 or 3 times a day. Do you still expect to get that released “this week”? As it by COB today?
Keep up the good work, folks.
Leon
4 months agoWhat advantage woulfd it be to utlise your technology on an old website that needs to be completely redesigned and brought up to date?
Ting
4 months agoThis post mentions “Performance in IE7/8”. Then what about the performance of Ext JS 4.1 in Firefox, especially Firefox 3.6? Will it be much better also?
Lawrence
4 months agoHello all. I have posted several messages in the forum but received no reply, so I try to ask here. I am sorry for the inconvenience. Can anyone tell me if the metaChange event will be inserted in the next releases? If not, what are the alternatives to use instead of the event? Thanks to all.
kprk
4 months agoHI Guys, any news on Release of EXTJS 4.0.7 for general community ?
Rashmi
4 months agoHi,
what is the expected release date for EXTJS 4.1 ??
Marc
4 months agoLooks like you should have been more conservative about communicating the date for the date for the release of 4.0.7 as well…
Mattis
4 months agoI would like to know release dates of 4.0.7 and 4.1 . Are you fixing scrolling issues in 4.0.7 and can you give performance figures on different browsers? Today I tryed to render a grouped grid 100 rows, 4 cols in 25 groups. It takes almost 5 seconds in FF4 - will this be solved?
Alan
4 months agoAny update on when 4.0.7 will be released?
Michael Mullany
4 months ago4.0.7 is now in final testing guys, we broke button toggling on Friday and had to fix over the weekend.
slemmon
4 months agoRight on. Thx for the update!
mistaecko
4 months agoGreat!
+1 for a 4.0.7 GPL release
+1 for making the bug tracker public (and if it is only read-only)
+1 for more communication and transparency
kprk
4 months agoThanks Michael for sharing news. Can we expect this weekend of early next week for release of 4.0.7 GPL
Matt
4 months ago+1 for making the bug tracker public (and if it is only read-only)
- Exactly… I cant be bothered filling bugs as its a lengthy process to do it properly (getting an isolated test case etc..) when I cant even see whats been filled already. E.g. adding a record to grouped grid after render time that has cell editing plugin enabled etc..
Does the property grid receive any treatment in 4.1 or is it still like bastard child where the parent has ran way and refused to pay maintenance?
Michael Mullany
4 months ago4.0.7 has been released to the general community and is available for download under both GPL and Commercial from the product section.
Christopher A. Petro
4 months agoWait. You seriously think the performance is “solid” on modern browsers? Because of the torrent of DOM updates the layout engine in Ext JS 4 issues, the app I work on is not usable on anything but Opera. It thrashes the caches in Chrome so bad that its performance is barely distinguishable from IE. I can’t tell you how relieved I am that I made the decision to dump Ext after you missed the first estimated release date for 4.1.
Andrew
4 months agoChristopher, what did you use instead? Extjs is about the cleanest looking product out there for application development. The list of bugs is a hundred miles long though. Looking forward to trying out 4.0.7 this weekend, thanks Sencha team for throwing us a bone…
Roger
4 months agoHave tested 4.0.7, still slow under ie8, and there’s a bug in multi-header which i did have before, drag the h-scroller bar , the header doesn’t follow the scoller bar. treestore crused while use treestore.load() to reload the store.
Aleksandar Ristic
4 months agoWhat about infinite grid in 4.0.7 ? Did you replace “virtual scrolling ” with “native scrolling” ?
Gian Marco
4 months ago@andrew there are many alternatives, Qooxdoo is a very attractive one beecause it’s very solid, well designed, has the most advanced toolset i’ve ever seen, has a very active community, is truly open source and has weekly updates with public repository and bugtracker.
Benjamin
4 months agoIt would be nice if there were some type of performance expectations set for 4.1. I can live with the delayed release dates if its going to perform when it comes out. If it comes out and its still doesn’t perform adequately - that’s going to be much harder to deal with. Can anyone say whether it will perform at least as good as 3.4? Hopefully Better?
Steve6000
4 months agoMore details please on what’s been resolved with Virtual Scrolling for Grids. I think this was of very high concern for many of us.
ordinary_guy
4 months agoYes, can you give an update on the scrolling issue as this is a very visible bug to our users in 4.0.2a. Many thanks.
Brad Schafer
4 months agoSencha - Although it might be related to the ‘grid scrolling’ issue posted in the forums, I have been unable to get the bottom bar to appear in a grid inside a tabPanel using the 4.0.7 release. If I revert to 4.0.0 the bottom bar appears fine.
João Paulo C. Marra
4 months agoGood one!
Extjs on the right path
M. S.
4 months agoToo little too late. This is the first project I consulted on that went down the Ext path and ended up scrapping it. Ext is fine if your making a basic static app but for anything with even the smallest interactions (which all serious web apps should have) it’s a bloody cow. I’ve been a full time EXT JS UI designer since 1.x.
The worst part of this last project is that I rebuilt the exact same thing and then some in jquery/slickgrid at lighting speeds in half the time. I’ll keep checking back though, just really really disappointed in the product so right now
Naz Ahmed
4 months agoExtJS Team - can we get a CLEAR and STRAIGHT answer on when 4.1 will be released and if all the issues related to grid scrollbar have been resolved. We took ExtJS with high hopes only to be disappointed. The ideas seems to be great but it has seriously failed to live up to its expectation
Comments are Gravatar enabled. Your email address will not be shown.
Commenting is not available in this channel entry.