Results 1 to 8 of 8

Thread: Migrating Extjs 4.1 to Extjs 6

  1. #1

    Default Migrating Extjs 4.1 to Extjs 6

    HI,

    We already have an EXtjs application which is developed with version 4.1 . We need to migrate to latest version Extjs6.x

    What will be the possible or exact way to migrate?
    Do we need to migrate Extjs 4 to extjs 5 and then extjs 6?
    Any document/steps which help to do upgradation to Extjs 5 or Extjs6?

  2. #2
    Ext JS Premium Member
    Join Date
    Sep 2009
    Location
    Cypress, Kalifornia
    Posts
    306

    Default

    There are probably notes about this on the Sencha website. We did the same migration and it was fairly simple. How difficult it will be depends on your coding standards.

  3. #3

    Default

    Where do i download Extjs 5.0.1 package ?

  4. #4
    Sencha Premium Member
    Join Date
    Sep 2014
    Location
    New Jersey
    Posts
    165

    Default

    Honestly - just jump to the latest version. As long as your app is structured and organized according to Sencha's best practices and their conventions, you'll be okay.

    This was just recently asked here where you can see some other responses: https://www.sencha.com/forum/showthr...2-to-extjs-6-6

    Also, you download all versions of the framework where you downloaded your current version at - in the sencha support portal.

  5. #5
    Sencha Premium User danguba's Avatar
    Join Date
    Feb 2009
    Location
    Kragujevac, Serbia
    Posts
    462
    All Best
    ---
    Željko Mitrović
    http://skitanja.blogspot.com/

    "Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live." Martin Golding

  6. #6
    Ext JS Premium Member
    Join Date
    Sep 2009
    Location
    Cypress, Kalifornia
    Posts
    306

    Default

    Oh yes, there was one area where we had to do busy-work/testing. Going from 4.2 to 6.6 there's a change in how it processes JSON. The property is Ext.USE_NATIVE_JSON which defaults to "true". This implies that it's using the browser parsing for JSON vs using low-level EXTJS code. In some cases your JSON parsing could fail unless you set it to false. We started with EXTJS 3, then moved to 4, then EXTJS 6. As such we weren't terribly disciplined in our JSON formatting from our server but the EXTJS code was forgiving, the browser default not so much.

  7. #7
    Sencha Premium User
    Join Date
    Feb 2011
    Location
    NJ
    Posts
    337

    Default

    I would also suggest upgrading right to the latest version instead of going to 5 first and then to 6.

  8. #8
    Sencha Premium User sdodierl's Avatar
    Join Date
    Oct 2017
    Location
    Paris
    Posts
    22

    Default

    if you want to switch from Ext 4 to Ext 6 classic, it should not be too difficult... provided you used ExtJS exactly the way intended.

    For us, switching from a heavily modded Ext4 (with nearly 100k lines of our own toolkit on top; our own data query system, our own navigation API, etc) to Ext6 Modern is a lot more costly.

    So it really depends how big your code is, and how complex it is.
    We're recruiting

    EcoMundo is looking for ExtJS architects and developers in their offices in 🇫🇷 Paris, 🇲🇬 Tananarive and 🇻🇳 Ho Chi Minh City!

    Check out https://www.ecomundo.eu/fr/recrutement or get in touch with me. We're a global actor in software for chemical regulatory compliance, with the size and state of mind of a start-up.

Similar Threads

  1. Replies: 0
    Last Post: 23 Jul 2014, 3:25 PM
  2. Replies: 3
    Last Post: 27 Jun 2012, 5:23 AM
  3. Replies: 5
    Last Post: 13 Apr 2012, 12:34 AM

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
  •