A couple of months ago, we published Sencha’s roadmap. Since then, we’ve received great feedback from you—our customers—and are making some updates to the 2019/2020 roadmap to incorporate your suggestions.
As a Sencha Product Manager, I interact with customers on a daily basis and am constantly amazed by the various ways businesses use our product. Because it is the most comprehensive JavaScript framework for building data-intensive, cross-platform web and mobile applications for any modern device, your feedback is extremely important in driving product direction, which makes our product the Best JS Framework.
Table of Contents
Continued Investment in Classic & Modern Toolkits
We’ve heard your feedback and tuned our goals. I think you’ll get excited, but don’t stop here. For customers developing applications with Ext JS Classic toolkit, we have enhancements in the works planned for the coming releases. For anyone developing with Ext JS Modern toolkit, you won’t have to worry about upgrading to any new toolkit either. Ext JS Classic and Modern toolkits will be first-class toolkits that will live long into the future. This means that we continue to invest in and provide feature and performance enhancements to both toolkits.
Sencha Modernization Mission
As part of our efforts to move Ext JS forward, we had previously announced the introduction of a brand new toolkit with the release of Ext JS 8.0 (codenamed “Sequoia”). Based on your valuable input and our analysis, we’ve discovered that a brand new toolkit supporting the modern JavaScript syntax is not necessary. Instead, we will continue to invest and innovate in further enhancing the current toolkits and leverage existing runtime to bring more value and options to our users.
- With any of the upcoming releases, upgrade lifecycles will continue to be smooth and incremental.
- You can continue to use the Classic and Modern toolkits in your current and future projects—and build applications with the products you know and love.
- Our engineering teams are working on a transpiler transform process that will allow you to write Ext JS classes and components with ECMA Class syntax. This process will be transparent to the developer.
- Our popular Grid component will be enhanced with new features. Grid performance and quality improvement will continue to be our focus.
- There will be significant improvement in the overall ease of use, accessibility and quality of all the components in our toolkits.
Our goal is to continually listen to feedback and be transparent in our roadmap and plans. We are laser focussed on improving usability, performance and deliver quality products.
What features would you like us to improve or add? Write back to me <[email protected]> or you can submit your requests via the support portal.
FAQ
Are you going to remove the Classic Toolkit in the future?
No, we’re going to focus on feature enhancements and improving its quality
Are you going to remove the Modern Toolkit in the future?
No, we’re going to focus on feature enhancements and improving its quality
I would like to use ECMA 2016+ language features, can I do that today?
Yes, you can do that with ExtAngular, ExtReact and ExtWebComponents. We’re also engineering a transpiler transformation process so you can write Ext JS classes with ECMA class syntax, which will be transparent to the developer.
Are you going to add more TypeScript support?
Yes, we’re going to aim to provide the Typescript definitions
What is Sequoia?
Sequoia is our code name for our major Version 8.0 where we are investing heavily in our framework improvements, modernizing and feature enhancements.
Note: These plans and roadmap represent our intentions as of this date, but our development plans and priorities are subject to change. Accordingly, we can’t offer any commitments or other forms of assurance that we’ll ultimately release any or all of the described products on the schedule or in the order described, or at all. These general indications of development schedules or “product roadmaps” should not be interpreted or construed as any form of a commitment, and our customers’ rights to upgrades, updates, enhancements, and other maintenance releases will be set forth in the applicable software license agreement.
It is more than one year that we still waiting GXT version 4.0.4, we are blocked on 4.0.2 due to the great amount of bugs and regression found in 4.0.3, and also we still having HUGE problems with the (payed) support, we have to wait weeks to get an answer and sometimes more!
I hope you will include a better support for the costumers during next year!
Hi Luca, I apologize with the challenges here. Thanks for the feedback! This is something we’re working on. We’ve assigned an additional resource to this area as well. I’m working hard to improve the delivery pipeline as a product manager. But the good news is GXT 4.0.4 is nearly complete, we’re just waiting for QE to finish, which will likely happen first of next year. We’ve had some delays in QA but we’re close to being done with many improvements that will fix the 4.0.3 issues.
It’s a really a very goood news that we don’t give up ExtJS classic tookit, because I think maybe users will prefer to move to other frameworks(react, angular, vue, .. ) instead of rewrite their ExtJS framework to ExtJS 8.0 …
Thanks again for listening ExtJS users :)
Great to hear! Thanks for your feedback!
For modern toolkit, enableColumnMoving and gridsummaryrow plugin is not working properly with lockedGrid, and formpanel’s getValue method returns wrong values if there were checkboxgroups or radiogroups.
Thanks for the feedback. Would you have support tickets for those issues? Or would you also like to try those in 7.1 to nightlies to see what’s fixed? I’m working hard to make sure issues raised are getting fixed quickly. Could you send them to my email brandon.donnelson (at) sencha.com
Brandon, thanks for responding on here. I’m not sure if you’re aware, but it looks like the nightlies on the support portal are broken. There are no nightlies for 7.0.x and none for 7.1.x either. Judging by some forum posts, I’m not the only one experiencing this. Is there some other place we should be looking for these?
I had forgotten to mention, the support portal, with some infrastructure changes going on, so we have delayed the nightlies delivery to for 7.1 to the support portal until the release. And I happen to be thinking of our delivery through the npm, so that’s my mistake. The Support Portal nightlies, I’ll see about getting those up soon. In the meantime would you be interested in testing through npm delivery?
After the ext7.0 modern treelist component is folded, repeatedly hovering and clicking on the child nodes have bugs. After the ext.dialog component is enlarged, there will also be bugs in the viewmodel. I hope that the next version will fix these two known issues
The bug also exist in Classic toolkit.
For us, commenting the listenter ‘refresh’ in Ext.tree.List method updateStore() fixed the pb. This event has been added in ext 6.7.0