Today we’re making available Ext JS 4.1 RC2, which contains bug fixes, enhancements and documentation improvements based on your feedback on our first Release Candidate two weeks ago.

The Release Candidate stage is all about polish, whether it’s on the framework, the examples or other sections like the documentation. Much of the work we have done since RC1 has been driven by the feedback we’ve received from the community; we’re always grateful for your bug reports and suggestions on the forums and we’re working hard to make the framework deliver based on your feedback.

Today we’d like to ask you to download RC2 and test it against your apps. If you haven’t used a 4.1 release yet we hope you’ll be pleasantly surprised by the performance improvements over 4.0.x, and if you have then we hope the additional polish since RC1 will make your apps feel and behave even better.

As we close in on a 4.1 GA release your feedback is more important than ever so we hope you’ll take a little time to test RC2 with your apps and let us know how it feels. We’ve prepared a full set of release notes and known issues for RC2, and we’ve put the latest examples online too.

Unfortunately though, in this release my application seems to be loading slower than it did under the beta 3 release. I get times of around 5-6 seconds with the beta 3, and around 10 seconds with rc 1 and rc 2.

There’s a bug in Chrome 18’s JIT code which breaks the Math object when code that uses certain routines gets compiled into machine code. That is the underlying cause of seemingly random layout problems on Chrome 18. We have submitted a bug report for V8, and we have a workaround in

Sorry, but I find yours job awful. My app, working very well with Ext 3.4 when passed to RC2 donne nothing. I would like use MVC architecture : with 4.0.7 it was nice but with with RC1 and RC2 I am completely stopped. Could you explain clearly what I have to change passing from Ext 3.4 to RC2 :
clearly, how to pass from a top-down traversal render method to the new method ?
I find the ExtJs the best framework for complicated applications but now I think to return to Ext 3.4 : not so elegant like MVC architecture but this is STABLE !!!!
Sorry, but I lost 2 months for nothing. I hope that next version will have more clear documentation

There’s no question, the programmers, and qa personnel working on 4.1 have been going above and beyond.

Yeah, there are some issues: performance, changing apis, bug tracking, svn/git access, announcements of release schedule. I won’t lie, these are pretty bad things. But, they have more to do with management decisions. I think we all can relate to management choices gone awry. I am sure performance issues were made clear to management early on.

My point is, let’s remember as developers to cheer on our comrades at Sencha. They are doing a great job developing and testing some really great software.

And, let’s not forget to target our angry woes to the right audience, the management. Let’s have public bug tracking; estimates on release dates; transparency transparency transparency.