Results 1 to 3 of 3

Thread: Upgrade from 4.2.: Modern vs classic toolkits (again)

  1. #1
    Ext JS Premium Member
    Join Date
    Jun 2011
    Posts
    280

    Default Upgrade from 4.2.: Modern vs classic toolkits (again)

    Hello,

    I'm still at 4.2.6 with a huge application based on Ext JS and I'm still wondering if I should put the work into upgrading to the newest version. This thought comes up every now and then (especially before adding a big new part to the existing code, thinking all the time: "Well, some day you have to upgrade all this stuff, too... is it worth putting so much detailed work in it now?").

    I found the Upgrade-Advisor (which looks good), but every time I'm digging into the upgrade-process I very soon come to the question whether to use Modern- or Classic-Toolkit. I found some discussions in this forum (like https://www.sencha.com/forum/showthr...assic-toolkits), but the general point still seems to be: "Modern will be the future, but it's not ready yet, because it lacks a lot of components which you might need."

    Currently my application is used only on desktops, but sooner or later someone will need to use a tablet or phone for it. Since the last discussion I found about this topic is for Ext JS 6.x, I just wanted to ask if there is something new about the roadmap that would tip my decision to one or the other side.

  2. #2
    Ext JS Premium Member mcouillard's Avatar
    Join Date
    Jun 2008
    Location
    Bucks County, PA
    Posts
    119

    Default

    The million dollar question!

    Yes, they released an update last Summer: https://www.sencha.com/blog/announci...nd-tooling-ga/
    Since 7.0 modern is now the recommended path forward even for desktop.

    An update to the roadmap was made later that year because many were worried about the lifespan of classic. Good news: it will continue to receive support: https://www.sencha.com/blog/updates-to-sencha-roadmap/

    So it may save a lot of time and effort first getting your classic app from 4 to 7. Then you can reconsider modern as a future step because by then it should be a lot easier to convert if needed.

  3. #3
    Ext JS Premium Member
    Join Date
    Jun 2011
    Posts
    280

    Default

    Thanks for your reply. I found that more changes are needed to convert the code from classic to modern, so I'm with your suggestion first upgrading to 7 with classic toolkit and then (perhaps) switching to modern toolkit.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •