1. 26 Oct 2012 1:28 AM #1
    deepak.sharma
    deepak.sharma is offline
    Sencha User
    Join Date
    Feb 2012
    Posts
    17
    Vote Rating
    0
    deepak.sharma is on a distinguished road
      0  

    Default Unanswered: What is the best approach to Migrating a webproject from Ext 2.2 to 4.1

    Unanswered: What is the best approach to Migrating a webproject from Ext 2.2 to 4.1


    What is the best approach to migrate a webproject build on Ext 2.2 to Ext 4.x? We are having difficulties as some plugins build on Ext 2.2 was used on that application.[ ColumnNodeUI.js, DDView.js, Ext.ux.DoubleInputField.js etc]. how to migrate them to Ext 4.x?
    Reply With Quote Reply With Quote
  2. 29 Oct 2012 6:04 AM #2
    mitchellsimoens
    mitchellsimoens is offline
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    St. Louis, MO
    Posts
    33,714
    Vote Rating
    438
    Answers
    3113
    mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of
      0  

    Default


    Hard to know without know what they do. Personally I would create the app for 4.1 and then recreate the plugins. A lot has changed from 2.x to 4.x
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    http://www.JSONPLint.com - Source to lint your JSONP!

    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!

    When posting code, please use BBCode's CODE tags.
    Reply With Quote Reply With Quote