[WP]joju (10/26/2009) well, as per EXT JS forums, extjs 3.0 contains a lot of memory leak fixes as well as extjs 3.1 which will also be out publicly next month i think. that's the reason we are asking about the extjs SVN...
I would just like to repeat, that we are keeping the ExtJS source for the v1.0 Toolkit up to date with the latest ExtJS SVN build... which is not necessarily the latest public release. You should generally not require both ExtJS svn access and the Toolkit svn access, since the Toolkit svn access should already be an up to date build of extjs.
We're monitoring the ExtJS rendering performance issues closely. We are implementing a few revisions and we will be incorporating ExtJS optimizations as they become available. If there is a critical fix only available in ExtJS svn, we'll look at the fix on an individual case and incorporate into the Toolkit if necessary. We've done that continually thought the life of the project.
I'll also repeat and stress the following...
If you require a fix committed to the ExtJS svn, just let us know. We might have already implemented the fix in our /trunk/, or could at that time.