Table of Contents
Over the past year, we have been listening to developers’ needs and we found that the majority of developers interested in Sencha are Enterprise Web Developers who are looking for:
- New beautiful components and themes to create great looking enterprise apps
- Modern tool chain to build optimized, performant, universal apps
- Productivity tooling for visual building of apps, visually theming of apps and IDE plugins
- Single place to source framework, components, theming and tooling
- Quality and test tooling to create enterprise quality long-running applications
- Upgrade path to standardized web components
We also received keen interest in Sencha’s products from Open Source Web or Mobile Developers who are looking for:
- Comprehensive component set for Open source frameworks – React, Angular, Vue
- Beautiful modern components with extensive API, layouts, visual theming and easy customization
- Modern tool chain to support latest in web tooling and web components
- Optimized components to build hybrid progressive mobile apps
With that in consideration, Sencha’s roadmap is centered around providing you with:
Most Comprehensive framework – Single maintained source to create long-living web apps. No need to source, integrate and maintain multiple libraries, components, plugins and tools
Cross-platform single code base – Maximize reusability of code for building universal and hybrid web applications. No need to write multiple apps for desktop, tablets, and smartphones
Open Tooling for development efficiency – Improve developer productivity by using modern and open tooling. No need to worry about “web tool-of-the-week”
Modern cross-framework components – Beautiful, themeable components with the framework of your choice. No need to rewrite hundreds of components for every new framework
Quality Web tooling – Minimize errors, reduce bug patches, and automate web application testing across different browsers. No need to search for different quality tools
Sencha – Latest Product Releases
Over the last few months we’ve had several exciting releases of Ext JS 6.6, with support for npm packages and open tooling, ExtReact 6.6 with support for the latest React framework, Sencha Test 2.2 release with inspect, code view, and page objects and GXT release with 100+ customer requested enhancements.
Sencha Product Roadmap Summary
The table below provides a summary of our planned development.
Detailed Sencha Roadmap
Ext JS Framework, Components, Premium Packages
Ext JS has long been the frontend framework of choice for developing Enterprise-grade web applications. We are working actively on the following:
- Advancing modern toolkit with new components
- Integrating high end components like Froala
- Enhancements, fixing bugs and increasing stability for both modern and classic
- Enhancing both the Modern and Classic grid and other components with fixes and new features
- Continue improvements to Graphite accessible theme and classic accessible components
- Determining approach for standardizing components with a web component model
- Giving access to Ext JS to all users making it easier to create applications
Ext JS Open Tooling, Build tooling, Fiddle, Docs
Open tooling involves the evolution of Sencha Cmd to an npm, webpack and node-based set of tools. The initial release of these tools involved creating a new application generation tool called ExtGen, and a supporting tool to begin to replace the functionality of Sencha Cmd in node called ExtBuild. The initial release created node-based application generation functionality, with other aspects of the tool (builds, watch, ext) relying on an integration with the existing Sencha Cmd tool. The initial version of the open tooling also only focused on the application generation process, leaving other aspects of the tooling to Sencha Cmd.
Future versions of open tooling will continue to replace functionality of Sencha Cmd with node-based modules. Also, more of the additional functionality of Sencha Cmd will be brought forward in the node-based ext-build module.
Open tooling will also continue to keep up with the latest ‘best practices’ for open tooling, such as remaining consistent with new versions of the selected tools, like webpack, babel and npm.
Ext JS Visual Dev Tooling – Architect, Themer, Inspector, Plugins
The main goal for the visual tools roadmap is to keep up with the incredible features and integrations planned for Ext JS, as well keeping plugins compatible with new IDE versions. A main focus will be around Sencha Themer, supporting ExtAngular and Ext Web Components, so you can still create beautiful themes for your applications, regardless of the underlying framework you choose.
In addition, a few long awaited features will be added to Themer, in particular, Custom Font Icons. It can be difficult adding custom font icon sets to your Ext JS applications. The goal is to make configuring your Ext JS themes to use custom icon fonts easy, as well as finally add support for changing glyph icons within the Themer application.
We are also looking at spending some effort to give Sencha Architect a much needed overhaul. One of the biggest complaints about Architect is the limitations around modifying the Ext JS code generated outside of the Architect application. The architect overhaul will likely come as a new product that will remove issues related to metadata requirement, which means you will be able to seamlessly switch in and out of this new ‘Visual Builder’ without worrying about breaking the tool.
Comprehensive automated testing has become an indispensable part of the modern DevOps toolchain, and it is our goal to make Sencha Test an indispensable part of our customers’ application development workflow.
We released Sencha Test 2.2 earlier this year, which added new features like Page Objects for managing locators centrally, a code tree view to help visualize test suites, new Futures APIs for interacting with HTML tables and Ext JS Slider component, enhanced the Inspect tool by adding a DOM Tree and also use DOM locators along with Ext JS Component locators. And finally, we added support for end-to-end testing of ExtReact applications.
Future targeted improvements include:
Allowing automatic minor updates to occur within the app – ensuring that our users always have access to the latest and greatest, and saving everyone the time and pain of downloading and manually upgrading their installs.
Enhancing the Sencha Test Futures API to include support for more high-level components and interactions, while keeping the ability to interact with low-level DOM elements. The event recorder will also be able to output scripts leveraging the elegance of the ST Futures API, which translates into scripts that are easier to read and maintain.
Enhancing the Inspect tool to improve our customers’ ability to easily, graphically create test cases quickly.
Extending the Sencha Test API to allow testing of ExtAngular applications.
The ExtReact product is an offering for the React developer community to provide access to the Ext JS components in familiar React/JSX syntax, access to the Ext JS layout system, a component theming environment through the use of Sencha Themer, and integration with Sencha Test for the development of unit and end to end tests.
The current version of ExtReact, version 6.6, focuses on the ability to support React v16x, Webpack 4 and Babel 7, which are the latest releases of these products. ExtReact also supports Ext JS 6.6 components.
Future versions of ExtReact will continue to support upgrades to the latest React releases, as well as tooling updates and innovations. Future support for the Web Components standard is also a consideration.
The ExtAngular product will be an offering to the Angular developer community with access to Ext JS components in a familiar Angular template syntax, access to the Ext JS layout system, a component theming environment through the use of Sencha Themer, and integration with Sencha Test for the development of unit and end to end tests.
The first version of ExtAngular is currently being architected, and will appear with the release of Ext JS v6.7. It will focus on integration with the latest 6.x release of Angular, as well as tooling in the form of Webpack 4 and Babel 7, which are the latest releases of these products. ExtAngular will also support the Ext JS 6.7 component set.
Future versions of ExtAngular will continue to support upgrades to the latest Angular releases, as well as tooling updates and innovations. Future support for the Web Components standard is also a consideration.
You’re going to see more of our examples with different configurations show up for GXT. It’s our goal to make it even easier to use GXT to write your structured web applications. Our goal is to continue to show all the potential features from the Sencha libraries you could use to build your scalable web application for your enterprise.
We’re planning on fixing over 50 issues in the next release, focused on addressing key customer issues. Our goal is to tighten up the testing and aim for better regression testing, so you have low impact on changes when you upgrade between minor versions. We want to make the highest quality Java web framework out there, aiming for better reliability and easier to use.
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 only in the applicable software license agreement.
On behalf of the entire Sencha team, we’d like to thank all of our customers and the growing Sencha community for their continued support and feedback. We look forward to our continued partnership. If you have any feedback you’re welcome to share at firstname.lastname@example.org.
William Clinton says
The article starts by mentioning “We also received keen interest in Sencha’s products from Open Source Web or Mobile Developers” but then doesn’t mention open source development or licenses at all.
There’s information about open tooling but that’s obviously not the same thing. I’m confused… Does the author think that that open tooling and open source development are the same thing?
Am I missing something? Other than the intro that seems to promise information of interest to open source developers, it seems like open source licensing has been completely left out of this document and does not exist on Sencha’s roadmap.
Sandeep Adwankar says
Thank you for going through the roadmap! Though we don’t have update to share at this point about open source, we have plans for some exciting announcements to share about Ext JS community edition next month. Pl. stay tuned!
Ivan Jouikov says
Thanks for the update.
How can you be quiet about removing the only feature that you posted on the previous roadmap, that would’ve justified version 7 being a major release, that is “Replace classic JS layouts with CSS flexbox”,
At the very least you owe the community a few lines like “we found it not to be technically feasible.”
NIall O'Brien says
Is that feature no longer going ahead?
Sandeep Adwankar says
Thank you for going through the roadmap and going through MVP community roadmap webinar last week. As discussed in the webinar, we heard from various customers to focus on bringing Ext JS modularization, best of the web standards, and open Tooling for development efficiency. Having said that, the roadmap is a living document and we are looking to hear from you if there are any aspects Sencha products that should be prioritized.
Oscar Giménez Bonet says
How about Visual Studio Code?
Sandeep Adwankar says
We do have Visual Studio Code plugin for Ext JS. https://marketplace.visualstudio.com/items?itemName=Sencha.vscode-extjs#overview
We do plan to update the plugin as part of future releases. Are there any specific features that you are looking with VS Code?
Oscar Giménez Bonet says
Can you please comment on Classic vs Modern.
Initially we had classic for desktop and modern for mobile.
Modern updated component and became modern for newer browsers. So it became a toolkit for mobile, tablet, desktop… but without feature parity with classic toolkit.
Modern is getting new features each release it will have, like 90% feature parity, with classic on version 7 which will come on 2019. Also in 2019 classic will continue to grow.
There are some projects, not only mine you can see in forum, that transitioned to modern to transition to classic again because of missing features. This is a bit frustrating and also a lot of work.
In 2017 and 2018 Classic can still be used to support “old” browsers, css… but time is going by and soon, if not already, old browsers will not be used. So the future of classic is rare. In a previous roadmap there was a comment to “modernize” classic and use new css… which would become the same as modern.
I want to use modern because that’s what you said the future was, but I can’t because until 2019 it won’t have many of the features used in classic, so i’m forced to use classic in some projects.
If I was project manager I would make an LTS of one of the toolkit’s only solving bugs and would center only on one toolkit. I like open tooling and many things you are doing, but I honestly think is time wasted because at the end of the day I can use whatever tools you have, cmd, npm… but I have to work on giving my customers the best experience possible and that is with a nice rich framework with all features for all devices.
It would be nice to have an official statement of the future of this two toolkit’s and let users know which one should they choose. EOL for windows 7 is January 2020, a year after version ExtJS 7. So what is going to happen? will classic converge to modern and make modern disappear? will modern get 100% feature parity with classic and classic will disappear?
Sandeep Adwankar says
We will continue to improve both Modern and Classic toolkit with customer feedback and requests as we have large number of developers using both toolkits. We would ask to evaluate your application requirements based on these toolkits and select modern, classic or universal patterns. Here are some details that may help you make those decisions:
Modern has some features which don’t yet exist in Classic, for example:
– Carousel Layout
– List Component
– Analog Time Field
– Dialog Component
– Date Panel
– Toggle Slider Button (on/off slider button)
– Material Design Theme
– Modern is optimized for mobile devices
With 6.7 release, Similar to Classic, Modern toolkit will have
– Multi-Select Combo Box
– Color Picker
– Grid filtering
– Grid locking
There are still set of Classic features that are currently missing from Modern and many of these will be added to Modern as part of roadmap. That include
– Spinner Field
– Form “isDirty” status
– Row editor (to make all fields editable in a row)
– Property Grid (a 2-column property and value grid)
– Reorderable grid headers via drag-and-drop
– Row body lazy creation
– Pivot grid cell editing plugin
– Desktop-style paging toolbar
– Locale support (47 built-in variations of languages)
– Table Layout
– Column Layout
– Accordion Layout
– Dashboard Layout (for laying out dashboard panels, and support drag-and-drop)
– Button Group
– Radio Group
– Check Box Group
– Box overflow menu
– Box / Tab reorder
– Breadcrumb toolbar
– Toolbar rotation (instead of just horizontal, also support vertical toolbars)
– Buttons acting as hyperlinks
Modern toolkit locale has 8 built-in variations of languages compared to 47 for classic and doesn’t have accessibility support similar to classic.
Oscar Giménez Bonet says
Chaya Chethu says
Thanks for Sharing this useful Information
Sandeep Adwankar says
Thank you !!
>>> Open tooling involves the evolution of Sencha Cmd to an npm, webpack and node-based set of tools.
I had a chance to play with the Parcel bundler, and IMO it’s fast and super easy to use.
Multiple experienced developers now claim that Parcel is going to replace Webpack, so the Webpack commitment could be reconsidered.
Watch these two videos:
Parcel …the Webpack KILLER?!
Using Parcel Bundler with React
Sandeep Adwankar says
Thx Les. We are happy with WebPack 4 for now, but we will continue to track developments in Parcel and capabilities compared with the Webpack.
Thank you so much for the informative stuff sir. Would like to become a fan of your writings.
Ganga Reddy says
Thanks for sharing this information.
What is the exact release date for 6.7 version ? .
We are on 6.6 modern version and waiting for Grid column locking and filtering features.
thank you for submitting this useful information.
Update Sencha route you share quite details. I have found many useful information for me.
redbox tv says
Nowadays many updates found on Sencha, it’s helpful to share with us.
happy wheels says
a very detailed and meticulous lesson, it really has a lot of values, I will learn a lot thanks
aos tv apk says
This update is absolutely helpful for all.
Amazing update well done thank you
streaming complet says
Thanks for sharing such a nice Blog.I like it.
Thanks for this post.