Sencha.com

Sencha

Ext JS 7.0 Early Access

| Binh Chau

We are excited to announce the release of the Best JS Framework that is for building data-intensive, cross-platform web and mobile applications for any modern device. Ext JS includes 140+ pre-integrated and tested high-performance UI components. Ext JS 7.0 can be accessed through the Early Access program. This release is packed with enhancements and exciting new features, with an emphasis on enhancing the Modern Toolkit. Read on to learn more about the release highlights.

New and updated Modern toolkit components:

  • Form Group (Checkbox, Radio Button) to easily group collection of checkboxes or radio buttons to support actions such as layout customization or validation at the group level.

 

  • Breadcrumb Toolbar, which provides the ability to present hierarchical information in a breadcrumb format.

  • Grid Updates, to support drag-and-drop row editing so that users can easily move, reorder and insert content in a row or cell.

  • Improved Accessibility in the Modern Toolkit with keyboard accessibility, tab-indexing and focusability.
  • Addition of localization package to Modern Toolkit for developers to easily localize applications for non-English languages. The locale package includes Dutch, Danish, Italian, Czech, Norwegian, Finnish, Russian, Korean, Japanese and Simplified Chinese.
  • The Material Theme with its minimalistic look and bold colors is now part of Classic Toolkit
  • Bug Fixes

Try Ext JS

We invite you to try out Ext JS 7.0 early access and share your valuable feedback via our forum.

What's your reaction?

0
0

Comments

  1. Mitchell Simoens says

    It makes me so sad to see how little Ext JS 7 is. Years ago, what Ext JS 7 was supposed to be was gonna be a huge update, this is more of a minor release (from what I’ve seen so far) as it’s just some new components. If you wanted to see what I mean and what Ext JS 7 was likely going to be, see what Don showed at the last SenchaCon: https://www.youtube.com/watch?v=QDiFi1rISnE

    This is the first major version since the acquisition and with people already fleeing the platform and the industry moving on, Ext JS 7 needed to be updated more than just iterating by adding a few more features.

    Also, not knowing who Binh Chau is, should have a couple sentences under the name at the end of the blog to tell us who the author is.

    Also, another note on this blog, the examples that are spelt out, can we get direct links instead of hunting in the kitchen sink for them? Like I found the checkbox group example but not sure what you mean by “Grid Collapsible Group” and I didn’t feel like clicking on different examples since I didn’t see any example with that heading.

    Reply

    • Mitchell Simoens says

      Maybe this should have been 6.8? But I can understand why sales department wanted a major version bump but nothing here tells me it’s a major version update.

      Reply

    • James M says

      +1 for Mitch’s comments. This blog entry was really done half-assed between the choppy images, formatting and no direct links to new examples.

      I am looking forward to new Ext JS, however, I just hope there’s more growth.

      Reply

    • Marc Gusmano says

      At first glance, the specific things that were added in version 7 do not seem to merit a new major version (many additions to the modern toolkit, especially to the grid component, – collapsible groups, row editing, reorder-able columns – adding check box and radio button groups to the forms package, more than 50 bug fixes) but what is unique about Ext JS 7 is that it is the culmination of several previous releases, in terms of the modern toolkit. For the past few releases, in 6.x, we worked on adding features and components to bring the modern toolkit coming to ‘parity’ with the classic toolkit, especially in the area of desktop components.

      We are also using the modern toolkit as the underlying component engine for ExtAngular, ExtReact and the new ExtWebComponents product, allows a customer to use the components in the modern toolkit with any framework that supports the Web Component specification, and most all of the popular frameworks to.

      Further, creating universal applications (an application targeting multiple device types) with just the modern toolkit provides for a lot more reusability in your application – so look at Ext JS version 7 as the introduction of the modern toolkit for all of your application development.

      So for all these reasons – the modern toolkit coming to parity with classic, the ability to build entire universal application with the modern toolkit and the ability for us to produce a set of modern components for any framework, it merits a new major release – Ext JS version 7.

      The next version of Ext JS, which we are currently working on, will take advantage of the new ECMAScript capabilities of Javascript such as classes and import/export as well as modern tooling such as webpack, babel, and npm. We are also innovating on our developer tools and are in the early stages of Ext JS Designer Tool within Visual Studio Code IDE. Check back for more updates.

      By the way. we have developed and released Ext JS Upgrade Adviser, which Don mentioned in the video. It will walk through your code and point out potential conflicts, suggest fixes and in some instances will auto-fix. It is available for free and supports upgrade from version 4.X to 6.X. Check it out here – https://www.sencha.com/blog/announcing-ext-js-upgrade-adviser-ga/

      Good question on who Binh Chau is… she is the Ext JS 7.0 product manager, who has done a great job getting us to the point of Early adopter release for Ext JS 7.0 – as one of the Architects on the product, I feel she is a major reason we are able to successfully release this EA, and we are on track to get the GA out shortly…

      Reply

      • Mitchell Simoens says

        Not sure I personally feel coming closer to parity with itself is reason enough for a major version considering there are licensing implications of going to a new major version. You are saying that there will be greater architecture changes to support newer specs and I assume this will be a minor version like 7.1 from what you are saying whereas such a change/addition would be much better suited for a new major version. This is like when we went from v3 to v4 going from using Ext.extend to Ext.define and all the changes allowed from that. 7.1 will see you marketing the new syntax, I personally just feel this was a sales decision and not an engineering decision and that raises a red flag. Yes, sales will always be a driving factor but it’s not the only one and not always the loudest unless behind the scenes things are greater than publicly known.

        I would also caution you with sticking with classes. This just isn’t where the vast majority of the industry is and using decorators is something that is very much hated by this vast majority. Angular is the only major platform that uses this and this is also a limiter for it, I learned this the hard way trying to get into React using classes and decorators and such, there were just more preferred ways that was a hurdle for me to understand but I now much prefer it myself. Without understanding where the industry is currently and is going, Ext JS will always be very limited and not achieve a comeback no matter what little updates you do… IMO

        Reply

        • Marc Gusmano says

          Mitchell, not sure what licensing implications you see for us going to a major version. Every customer who is current on support gets every new version – we do not charge extra when we bring a major version out.

          As far as architecture changes go, we have learned through the v4 to v5/6 architecture changes that customers do not want breaking architecture changes if not necessary, and currently we do not have any needs for breaking changes. Customers want to be able to upgrade to a new version as smoothly as possible. We don’t feel that the only reason for a new version is then there are breaking architectural changes…

          Reply

          • Mitchell Simoens says

            Come on Marc, you’re a sales guy you should know licensing. You only get access to the next major version release if you purchased the last major version within 12 months. That means, say 7.0 GA was released today and if you bought v6 before July 12th 2018, you don’t get access to v7. This is spelt out on your licensing page. https://www.sencha.com/support/#standard-maintenance

            Also, support for v6 ends 2.5 years after v7 is released so if 7.0GA was released today, those on v6 would not get support after January 2022 which is a long time away but that is still an implication some are not comfortable with upgrading. You have to admit we’ve had issues with people staying on older versions.

        • Marc Gusmano says

          As far as the EXT JS approach to classes – yes we do have a rather unique approach – the config approach you are very familiar with.

          There are customers who rely on this approach – it, for example makes for creating a ‘dynamic’ view created at runtime much easier than the custom element approach.

          For those customers who desire an approach like the newer frameworks provide, like, for example React with JSX, we have a solution – ExtReact.

          And, now with the introduction of ExtWebComponents (EWC) in version 7, we now support the Web Component specification, and most of the popular frameworks either fully support the spec or are close – for example, this website shows major frameworks support:

          https://custom-elements-everywhere.com/

          I do remember reading a blog of yours where you advocated the Web Components approach – so I assume you are in line with this.

          The work we are doing with the next version of Ext JS taking advantage of the mew ECMAScript features in JavaScript will be applied to EWC to make that product even more compelling – no matter what framework you use

          Reply

          • Mitchell Simoens says

            ExtReact and other bridges are a non-starter for me personally. Ext JS is just too big so not only would I have to load React, I have to load Ext JS and while I know that doesn’t mean loading ext-all.js, you can quickly get to a large bundle size quickly with Ext JS. Ext JS also does things that are not needed today with new specs or alternatives. For example, I know lots of people have asked me about what to do with React without a data package like in Ext JS and the answer is, you don’t need a data package. The data packages is just a store (an array of objects), you can sort and filter an array easily (even if you need to use lodash or something if you aren’t comfortable with doing it yourself), you can load easily (using fetch api or there are lots of modules to handle other types but so far, fetch has been all I’ve needed) and reading is easy as 99% of what I do is JSON but even if it’s something else like XML, that’s easy to parse and there are modules to do that for you. The benefit of Ext JS, it’s all built into one thing but the downside to that is that bloats the size as supporting everything will no doubt have dead code and tree shaking is a no go for Ext JS. Another example of this is the text field. I’ve not needed a text field that supports triggers to the extent that Ext JS supports. Sure, add a clear icon but that is simple to do without all the work to support triggers.

            Yes, I am a huge fan of web components and have said many times publicly that I feel they are the future but I also don’t feel like what you call a web component is a web component, it’s just a way to get node attributes to a config object and a place for Ext JS to render in to. There is far more work to truly be a web component and from what I’ve seen Idera is more concerned with legacy code than what it would require. But that’s my opinion.

            I also understand why you are trying to point out products that allow you to check off features but if you go deeper than a feature sheet, the features start not to hold their weight. But once again, that’s my opinion.

          • Marc Gusmano says

            Mitchell, I think you gave me an idea – your comments on our component products, ExtReact, ExtAngular and now ExtWebComponents are best answered in a blog – which I will start on.

            I think there is a thought that because we have an initial strategy to bring our existing components to React, Angular and other frameworks that there are inherently somehow slow – quite the opposite! I feel I need to explain all of this in a blog with examples – so thats what I will do!

            I will try to get that out to all of you next week – thanks

          • Mitchell Simoens says

            Thanks Marc, glad I could help (I’ve been giving you lots of feedback to help). I don’t think the bridges are slow, I think Ext JS is slower than it needs to be but I know that it would take lots of work to get it into shape for today’s browser and tooling support. Not something you can just enable with the current codebase.

          • Marc Gusmano says

            Mitchell, we are making very good progress to implement the new ES6-ES8 JavaScript standards into Ext JS. Todays browser and tooling is also very important to us – our products are now embracing tools like npm, webpack, babel – and we continue to further that innovation to the new tools.

            On the tooling front, one project of note is the work we are currently doing to implement an Ext JS Visual Designer in Visual Studio Code as a VSC Extension – as soon as we have something we can share with all of you we will.

            And, we are also architecting this next version of Ext JS with a focus on modularization – in this new word of frameworks that need components, we recognize that is further needed.

            As you mentioned, even with the current Ext JS architecture not being as modular as we like, we are still able to do the necessary treeshaking to provide the performance needed for ExtReact, ExtAngular and ExtWebComponents – demonstrating this will be the focus of the blog I mentioned I am working on…

      • ElCondor1969 says

        Hi Marc Gusmano.

        I want to take advantage of your post to ask you for information about ExtWebComponents.
        Will it be possible to use both classic and modern toolkits with ExtWebComponents? Or will they only be limited to the use of the modern toolkit?
        This is very important information in my opinion because the classic toolkit in many cases is still the most profitable choice for certain types of desktop applications.

        Reply

        • Marc Gusmano says

          We are implementing ExtWebComponents with the modern toolkit – I am curious what you mean by “the classic toolkit in many cases is still the most profitable choice for certain types of desktop applications” – can you elaborate on this statement. What types of applications are you referring to? What is missing from the modern toolkit that would need to be added?

          Reply

          • ElCondor1969 says

            Hi XXX.
            What I want to say is that there are apps designed to be run only on desktop PCs or notebooks. In these cases the App doesn’t need to be “responsive” and therefore it can have the advantage of enjoying more ad hoc features and losing generality.
            Consider, for example, how many more layouts the classic toolkit provides compared to the modern toolkit.
            As you know, the APIs of the two toolkits are neither equivalent nor equal and considering an APP for a desktop PC, the classic toolkit is the most advantageous in terms of functionality.
            That’s why, in my opinion, the new WebComponents should not neglect also the classic toolkit. If you didn’t, it would be a mistake for me.

          • ElCondor1969 says

            Hi Marc.
            I’m sorry if I wrote XXX but obviously I meant to refer to you.
            Forgive me again for the typo.

          • Marc Gusmano says

            ExCondor, thanks for the feedback – I will make sure Aria support is in our discussion for the modern toolkit. I am curious, though, which layouts you feel are missing from the modern toolkit. I do know, for example, we don’t have a border layout, but you can easily create one with the current layout capabilities of the modern toolkit. Are there other layouts you feel are missing? Is there anything else you feel is missing from the modern toolkit?

          • Marc Gusmano says

            I didn’t mean ExCondor… meant ElCondor – I guess we both have an x problem while typing… :)

          • ElCondor1969 says

            Yes Marc, border layout is just one of those layouts that most makes itself felt in the modern toolkit. But it’s not the only useful layout to be missing.
            You ask me to list the various reasons why the modern toolkit cannot be equivalent to the classic toolkit.
            Marc, it would be really too long to list the technical reasons for such a difference but just look at the two Apps to have the confirmation of their diversity. Also, just talk to any technician within your company to confirm that, in the context of an App running exclusively on a desktop PC, the classic toolkit offers many more features, and better, than its modern counterpart. Or at least that’s my opinion.
            So I really hope that you Sencha do not neglect the classic toolkit in favor of the modern toolkit within your new products.
            If I understand well that managing a single toolkit for you is much more efficient, it is equally true that neglecting a product (which already exists) that offers more advantages under contexts certainly not niche (such as desktop apps) is another deleterious choice (and already Sencha has made several wrong choices in his past, such as the famigerate question of the package of five licenses for ExtJS).

        • Marc Gusmano says

          Tim, you are correct, full ARIA support is currently available in our classic toolkit. We have discussed implementing full AREA support in our modern toolkit, although there are a lot of capabilities related to AREA already in our modern toolkit. I am not the expert on Area, if you would like, contact me directly and we can discuss forther

          Reply

        • Dawesi says

          agree… classic is a first class citizen IMHO.

          Modern is pretty, but it’s easy to make classic pretty also.

          Until ALL of the features of classic are in modern it’s a non starter for complex data interfaces ATM.

          Also border layout is more than a few flexboxes thrown together… (a lot more…), it’s also been a core features of ExtJS since layouts were introduced. Not sure why you’d want to depreciate it… #noideawhy

          Reply

          • Don Griffin says

            See my comment below on docked/panel collapse for equivalent functionality to border layout in modern (since 6.5)

    • Marc Gusmano says

      Mitchell,

      Good idea on providing direct links to the examples for whats new in Ext JS 7 – here are those links…

      Ext JS Modern Toolkit enhancements
      * Froala Component integration
      https://examples.sencha.com/extjs/7.0.0/examples/kitchensink/?modern#froala-editor
      * Grid
      Drag and Drop – https://examples.sencha.com/extjs/7.0.0/examples/kitchensink/?modern#big-data-grid
      Row Editor – https://examples.sencha.com/extjs/7.0.0/examples/kitchensink/?modern#row-editing
      Collapsible Groups – https://examples.sencha.com/extjs/7.0.0/examples/kitchensink/?modern#grouped-grid
      * Tree
      Drag and Drop – https://examples.sencha.com/extjs/7.0.0/examples/kitchensink/?modern#tree-reorder
      * Layouts
      Accordion – https://docs.sencha.com/extjs/7.0.0/modern/Ext.panel.Accordion.html
      * Form Components
      CheckBoxGroup – https://examples.sencha.com/extjs/7.0.0/examples/kitchensink/?modern#form-checkboxgroup
      RadioGroup – https://examples.sencha.com/extjs/7.0.0/examples/kitchensink/?modern#form-radiogroup
      * Toolbar
      Breadcrumb – https://examples.sencha.com/extjs/7.0.0/examples/kitchensink/?modern#breadcrumb-toolbar
      * Localization – 10 additional countries
      Dutch, Danish, Italian, Czech, Norwegian, Finnish, Russian, Korean, Japanese, Simplified Chinese
      * Accessibility: Keyboard/Focus Management, Tab Indexing

      Ext JS Classic Toolkit enhancements
      * Material Theme
      https://examples.sencha.com/extjs/7.0.0/examples/kitchensink/?classic=&profile=classic-material#all

      New – ExtWebComponents
      https://examples.sencha.com/ExtWebComponents/7.0.0/kitchensink/

      Reply

    • Les says

      >>> see what Don showed at the last …

      I watched the video again. Don is mostly talking about class improvements in Ext JS, but this is not the direction modern JS frameworks are going these days. The current major JS frameworks are highly reactive and their class based APIs are generally abandoned.

      Reply

      • Marc Gusmano says

        Many customer rely on and like our JavaScript config-based approach – and have build some really unique solutions based on that ability.

        We also recognize and see frameworks like React, Angular and Vue and their approaches – and they are great approaches – but one thing that is missing from all of those frameworks is robust, data-oriented, tested, proven components – and thats why a part of our strategy is to have products like ExtReact, ExtAngular and now ExtWebComponents!

        So as our customer, you can choose the framework approach you like – and you are able to utilize our components in any one of those frameworks.

        Reply

  2. Mitchell Simoens says

    It says this blog has 2 comments but then doesn’t show any comments. These two were from me, are they awaiting moderation or something? I don’t remember saying anything out of line even.

    Reply

    • Marc Gusmano says

      I hope you have read all the comments I have made in this post – if there are actual things you think we could do better, or strategies (which we have published in our milestones – another one coming soon), we want to hear about them – not sure what your comment actually means…

      Reply

  4. harryBundles says

    Still can’t navigate the sample dashboard with my keyboard. When will ExtJS add full accessibility support? Also, Mitchell Simoens, it’s very cool to see you still trying to make Sencha great. It’s sad what it’s become.

    Reply

    • Marc Gusmano says

      making the sample dashboard a true set of components and not a sample is slated in the next release… although we do have a set of requirements for it, I would be very interested to hear what you are looking for in the dashboard – and how you see the keyboard navigation you mentioned working – if you have some requirements you can send to me I would appreciate that

      Reply

  5. Vadim says

    Another fake major release just to milk money from licenses. Everyone have expected 7 to be something major and include what Don has shown at the SenchaCon. Probably you can cheat customers, but not us developers, and without devs, customers can’t build anything, eventually they will run too to the other communities.

    Reply

    • Marc Gusmano says

      Hi Vadim, I just responded to Mitchell in the above comment – the work Don demonstrated at SenchaCon is currently being developed – we already have the code and data package at a usable state. Maybe I can put together a demo and perhaps a blog to give you an update on this… in the meantime, feel free to ask me any other questions

      Reply

  7. Speed Talton says

    I stopped by to see if anything has changed since I dropped my subscription which would cause me to want to re-subscribe, but I don’t see anything of value to me.

    I started using Architect (versions 3 – 4.2.3) in the hopes that it would do as promised but it just never evolved into a good IDE.

    All the focus is on adding features to Ext instead of making it easy to develop cross-platform in a visual design tool. My needs are probably not a big priority but I do hope that someday some forward thinking company will come out with a visual designer with a compiler which will catch errors as you work.

    It seems now that Sencha merely promotes their components for use in other company’s frameworks. They aren’t interested in Architect being anything great for people like me.

    btw, I always appreciated Mitchell’s help and comments on the subscription forums-he knows what he is talking about. He adds value to the Sencha products.

    As an aside, the subscription is too costly. X-credits were a joke. To be fair, there are some good tech support people but literally no one could help me much with Architect. They just did not know a lot about it–and it was obvious to me they did not use it.
    Example: It took over two weeks to have support come up with a way to make a toolbar be responsive (in Architect). Two weeks! Nothing else, just a toolbar in an otherwise empty project. And it required writing the code. That was it for me. Sencha says that Ext is the bomb, but Architect either didn’t support all its features or they aren’t available unless you literally write all the code yourself…so why pay for Architect?
    This is only my experience, that’s all I can say.

    Reply

    • Marc Gusmano says

      As far as a visual design tool goes, I wanted to make you aware that we are in the middle of a project to provide for visual design capabilities for Ext JS within the Visual Studio Code IDE. We chose the VSCode IDE as our initial IDE platform based on its popularity and availability and extensibility (personally I use VSCode as my everyday editor now…). Be great to discuss with you what capabilities you would like to see in this tool, and as soon as we have enough to demonstrate, we certainly will be doing that

      Reply

  8. Mario Alvarez says

    For an early access blog post about a new major version, this blog post seems very very rushed, seems like the author had only 10 minutes to write it.
    Major versions should catch people, this one doesn’t cause that effect IMO.
    As Mitchel said before, this really looks like a minor release…
    Really sad to see such a big project like this going down and down…

    Reply

    • Marc Gusmano says

      I did reply to Mitchell on this above – take a look. FYI, we will be publishing our revised roadmap soon to further discuss how Ext JS 7 fits into our strategy, and also discusses releases beyond 7

      Reply

  9. Daniel da Cunha Bueno says

    Hello Marc,

    I want to do a job of spreading the new version here in Brazil, but I was left with some doubts, if you can answer me, because I must record the video this weekend for youtube channel from my company.

    1. In the Sencha Community Days event in Karlsruhe (Germany) one of the things presented to us is that the projects will run with the new syntax javascript, I noticed here by the comments that this will still be implemented, you have notion of how much time for this to be available?

    2. At the same event, it was commented that there would be a plan for users to have a degree license up to a billing threshold for one or more projects. I wanted more commercial details about this initiative, because here in Brazil we will have potential sales of framework licenses, but they will want to fully experience the potential before making the purchase decision.

    3. I missed some components that were pointed out in Early Access, but I noticed that other people are commenting on the same problem about the Kitchen Sink sample page.

    Tks.

    Reply

    • Marc Gusmano says

      Hi Daniel, be happy to help you in your efforts and get you what you need – please feel free to contact me directly…

      I did comment on your point number 1 in the response to Mitchell above – take a look and let me know if you have any further questions

      I am not sure I understand number 2 – I am not aware of a billing model from us based on any threshold – if you can clarify it I can get you an answer

      for number 3, I posted a set of links in response to the same question above…

      Reply

  10. aostv says

    Thank you very much for the early access dude, I really enjoy JS v7.0 heart fully. Also, I have come to know that it’s the most successful version ever in the history of JS.

    Reply

  12. Alexei says

    Hello Marc,
    It looks like I’ve missed something…
    If you check the post from https://www.sencha.com/blog/sencha-product-roadmap-update/ , ExtJS 7.0 (2018 Q4) was supposed to have “CSS Driven Layouts”.
    Was that huge improvement postponed or removed at all? Where I can find an actual roadmap?
    Looking at comments, I can read between the lines “use modern toolkit”, but I’m very skeptical about changing toolkit type of ExtJS framework in a big commercial project for that kind of reason.
    Best regards,
    Alexei

    Reply

    • Marc Gusmano says

      Hi Alexi, we do have CSS Driven Layouts in the modern toolkit – that comment was the potential to also add them to the classic toolkit.

      The roadmap you linked to is about 1 1/2 years old, and we have evolved out thinking about adding CSS Layout to classic vs some other efforts – we will have another revised roadmap out very soon (as a blog) to continue to keep everyone posted on our vision for the product – as always, any specific questions please feel free to ask…

      Reply

  14. Cesar Segura says

    FEW things for a major version is very disappointing. Like Mitchell said , not like a huge major update. But also in overall view since the initial release of Version 6 just few things for modern and nothing for classic ?

    WEB Components as described by some people I know checked the trial told me that 60% of examples is plain EXTJS using npm and the other 40% ifs like a porting version of Extjs to web components and also not so good. So if its the same as Extjs why to consider it as a new whole product ?
    Many new stuff its for the PREMIUM plan and nothing for the PRO or STANDARD (this is not the case because its extjs). and I’m not talking about Architect updates or Themer updates. Also why Angular and React only , also Brytnum released Scheduler, Gantt for Vanila JS VUE, Angular and REACT same code for all of them, Why not sencha?

    My perception is that Extjs in Angular is one product, Extjs in React another product and so on.So this should be part of Extjs itself and not being considered another product.

    Finally Sencha has arrived at the point similar to Where “MANY USED TO BE GOOD ” products are right now (and its not fault of current owners). They were created by the community , all companies accepted and liked Sencha due developers all around the world,. But the company Struggle wanting more money and the products lost the soul of “WHY” it was developed. Then began to consider only HUGE companies and the small/freelance developers and community was forgotten.

    Sencha was sold but new Owners instead of making a whole new approach/path/way to regain the lost community/developers keep almost the same path with the exception of the Famous “Single license” (I will not blame future/past Sencha developers , they just follow instructions) But come on guys you can do better.!

    SO people/developers/companies (small and medium, not considering the big ones) with support plans (STANDARD and PRO) let’s say that they/we have been paying around 2-3 years of support plan just to see this ???

    So far I can say that Extjs Version 3 and Version 4 without the new modern Javascript (node, npm , babel, etc, etc…) are the best releases and still right now are the best products releases and even if you integrate those versions to modern Javascript stuff and combine with Vue, React, Angular THEY really work very good.

    Reply

    • Marc Gusmano says

      Hi Cesar, have you actually tried using our ExtWebComponents product? I think if you did you would have a different opinion of the product – it actually does do a lot of what you are asking for – works well with all current frameworks – even React, that has synthetic events – there is still a way to provide for properties and events.

      And it can work with modern tooling – we support webpack and babel – you can use any data access strategy you would like – any layout environment (plus you can use ours within the web components!), and anything else you may want to do in a modern JavaScript application. I would be happy to get you up an running so you can see this for yourself – feel free to contact me. And if there are others who would like to see the product, I would be happy to set up a GoToMeeting to do so – Marc

      Reply

      • Cesar Segura says

        Well I mean personally I havent tried Web components cause as tradition with Sencha releases since version 4 the initial releases will be very buggy still.

        But mainly my wish/hope is that WEB components has to be part of the same EXTJS product and not another different product. I think if i have 1 or many Licences of EXTJS i should have be able to use Traditional (javascript) EXTJS with sencha cmd or EXTJS-WEBcomponents in VUE or REACT (using npm, webpack etc). So whatever the way i want for my developments with same license and not pay twice or pay more for the same thing (which could be an aggregated Value to the Framework and make it worth it to regain the lost market). An Im talking that not just only premium but for Pro or Std.

        Also there is no page for Extjs -VUE , documentation is still as traditional JS, for someone who knows ExtJs classes and how EXTJS works it should be no problem (just looking at samples) but for new developers (with no Extjs experience) and want to begin how they will know how to use them ? because they may figure out checking samples but looking at documentation they will have to look old docs and figure out how to set properties not used on samples.

        I mean at the end you decide the strategy , just im trying to express my point of view of what i may consider to Make EXTJS more attractive to me and for other single developers.

        Reply

  16. Westy says

    Wow, that’s the most comments I’ve seen on a Sencha blog post in years, although admittedly, I’ve not been that active on here for years!
    Shame they don’t seem to be very positive. I must admit it sounds like a 6.8.0 to me rather than a major release.

    Regardless, I’m currently in the process of upgrading from 5.1.0 to 6.7.0, so won’t be looking at this for ages. Sounds like I’ll also be trying to change from classic to modern toolkit too, which will break 80% of our overrides…

    Hopefully most of the bugs and missing features (like tab orderer and border layout) will be added by the time I get around to it.
    Yes, I know can make an equivalent to border easily, but when you have existing code I’d rather not…

    Cheers,
    Westy

    Reply

    • Don Griffin says

      Fwiw, border layout is not needed in modern. Just use panel collapse and docked items in the viewport (or whatever container). The animation behavior of panel collapse defaults to the same as the classic border layout. You can tweak that w/dynamic config

      Reply

  17. Dawesi says

    Is the visual editor the rewrite of Sencha Architect & Sencha Themer?

    Does this mean SA / Themer are dead? Will there be another update? Will it be open sourced so we can unlock the application node to create basic classes (still waiting for that fix… so many promises, no delivery, super easy tweak) fix bugs and add features to it (until the new visual editor is at parity) Looking forward to seeing it.

    Will it allow plugins? (aka to create hooks to autocreate tests (for Siesta or 3rd party js tools) or for us to write code generation tools alongside the sencha plugin? we were promised this in v2.x of SA)

    What versions of ExtJS will visual editor support?

    Will you be able to import / export code?

    Is there an early release?

    Reply

    • Marc Gusmano says

      Sencha Architect and Sencha Themer are being updated for Ext JS version 7 – which will be generally available in August

      We are early in the process for the Ext JS Designer I mentioned – we are doing a POC within VSCode – as soon as we have more to share on this, we will

      Reply

      • Andrew says

        I really really really hope Architect doesn’t go away. While it’s not the best I’ve found it to be extremely valuable as a tool for getting newer devs into the Sencha ecosystem. I bought architect for $129 when it was released and at that price I would tell everyone and their mother to use it. If it wasn’t so expensive and burried away under the $6k package then I bet you would get more users. Give it away for god sakes and maybe people will use it and buy more licenses! BTW There is a single developer license link on your pricing page which currently takes you to a 404. This is kind of ridiculous.
        “Price (For up to 5 developers; includes volume discount.
        View Single Developer Subscription License pricing.)”
        https://www.sencha.com/store/extjs-subscription

        Sell architect separately for a reasonable price. Probably worth $250 right now. Maybe if you add more features and fix 6.7 upgrading (currently broken) it would be worth more.

        If you’re going to kill it just please release it open source so folks who have invested a lot of time into it such as my company aren’t totally screwed. I will find another product if I get burned on that.

        Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Subscribe to Sencha newsletter

Sencha is committed to protecting and respecting your privacy. For further details on how your data is used and stored, please review Sencha Privacy Policy. You can unsubscribe from these communications at any time.

Sencha.com

US: 1 (800) 212-2802

[email protected]