Ext JS 3 to 4 Migration http://www.sencha.com/blog/ext-js-3-to-4-migration Ext JS 4 is the biggest leap forward yet for the framework, and upgrading an existing application from Ext JS 3 can be a daunting challenge. You’ll learn about the brand new Ext 3 to 4 Migration Pack, a bundle of resources we created to make this transition easier. We’ll also introduce our two-part video tutorial that walks you through migrating an application step-by-step. en-us brian@sencha.com Copyright 2011 2011-05-02T19:05:34+00:00 Comment by Smalltalker I have >20 years experiance in Smalltalk and about 1 year in Ext 3. Looking at Ext 4, I get the impression that you have learned and re-used a lot from Smalltalk - and that is very good, because this “granny” is stil superior to all the kiddies, including JavaScript. As for your “OO JavaScript” you would have better re-used a German development called JOOP, which has it all (and more?). It was made by a Smalltalker (not me). But of course, for USA people it’s always a huge problem and matter of pride to optain things from Europe. The “not invented here syndrom”. We know…! I have >20 years experiance in Smalltalk and about 1 year in Ext 3.

Looking at Ext 4, I get the impression that you have learned and re-used a lot from Smalltalk - and that is very good, because this “granny” is stil superior to all the kiddies, including JavaScript.

As for your “OO JavaScript” you would have better re-used a German development called JOOP, which has it all (and more?). It was made by a Smalltalker (not me).

But of course, for USA people it’s always a huge problem and matter of pride to optain things from Europe. The “not invented here syndrom”. We know…!

]]> Sat, 27 Aug 2011 12:58 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:25984#date:12:58 Comment by Jesse Excellent work… Excellent work…

]]> Sat, 20 Aug 2011 19:46 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:25535#date:19:46 Comment by Rajasekar Really good work brain… Really good work brain…

]]> Wed, 27 Jul 2011 04:51 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:24562#date:04:51 Comment by Hallie That’s going to make things a lot esaier from here on out. That’s going to make things a lot esaier from here on out.

]]> Sun, 26 Jun 2011 19:56 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:23416#date:19:56 Comment by lockng @anonim ... “Even from UI point of view there are mistakes, for example you don’t have a class that could act seamlessly as a command button or menu item depending on the container. If you need both a button and a menu item, you have to create and maintain each one separately or write your own class.”... You do not have to create a “new class” to handle this… you use Ext.Action and create many menus or buttons from the action…. @anonim
... “Even from UI point of view there are mistakes, for example you don’t have a class that could act seamlessly as a command button or menu item depending on the container. If you need both a button and a menu item, you have to create and maintain each one separately or write your own class.”...
You do not have to create a “new class” to handle this… you use Ext.Action and create many menus or buttons from the action….

]]> Wed, 22 Jun 2011 15:45 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:23259#date:15:45 Comment by Sergey Borovsky Not a slightest chance that our application is going to be migrated from 3 to 4 with this simple migration package. We’re using (rightly or wrongly) DWR for AJAX. That’s where EXTJS 4 stops working from very beginning. Not a slightest chance that our application is going to be migrated from 3 to 4 with this simple migration package. We’re using (rightly or wrongly) DWR for AJAX. That’s where EXTJS 4 stops working from very beginning.

]]> Fri, 17 Jun 2011 19:08 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:23060#date:19:08 Comment by anonim @lossendae ExtJs design was UI, and not Model oriented. It suffices to look at the extensive changes in Grid and DataModel to see what was wrong. For example the Record validation is done in the UI, more specifically in the Form. If you need to change a record in other way than trough the UI, you will have to duplicate the code for validation. Also the validations rules can be different for update and insert. If you change a field name, you have to modify in the at least three places, Grid, Form, Store. If you used more than a couple of grids and forms in an application, you should be already aware about these problems. To avoid such things we designed our own data model library, but now we have to rewrite it to make it compatible with ExtJs4. Even from UI point of view there are mistakes, for example you don’t have a class that could act seamlessly as a command button or menu item depending on the container. If you need both a button and a menu item, you have to create and maintain each one separately or write your own class. @lossendae
ExtJs design was UI, and not Model oriented. It suffices to look at the extensive changes in Grid and DataModel to see what was wrong. For example the Record validation is done in the UI, more specifically in the Form. If you need to change a record in other way than trough the UI, you will have to duplicate the code for validation. Also the validations rules can be different for update and insert. If you change a field name, you have to modify in the at least three places, Grid, Form, Store. If you used more than a couple of grids and forms in an application, you should be already aware about these problems. To avoid such things we designed our own data model library, but now we have to rewrite it to make it compatible with ExtJs4.
Even from UI point of view there are mistakes, for example you don’t have a class that could act seamlessly as a command button or menu item depending on the container. If you need both a button and a menu item, you have to create and maintain each one separately or write your own class.

]]> Wed, 01 Jun 2011 13:28 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:22188#date:13:28 Comment by lossendae @anonim Seeing “ExtJs was poorly designed from the very beginning” and later “switching to a more mature framework, or even developing a wrapper around other lighter and stabler libraries such as jQuery” is… not very accurate. @anonim
Seeing “ExtJs was poorly designed from the very beginning” and later “switching to a more mature framework, or even developing a wrapper around other lighter and stabler libraries such as jQuery” is… not very accurate.

]]> Tue, 31 May 2011 14:45 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:22121#date:14:45 Comment by anonim @Anon: The truth is that ExtJs was poorly designed from the very beginning and there where no choice than complete redesign of some modules, of course with the price of sacrificing compatibility. I am in the same situation as you and I don’t know if I will ever upgrade. JavaScript is not Java or C++ where compiler does most of the job, you need very skilled developers to overpass the lack of tools. We also have some applications written in ExtJs2, that will never by upgraded. Rewriting a corporate applications from scratch every year because of unstable framework features is very expensive, and you will never get budget for that since the application is working fine in the eyes of the management. We are considering switching to a more mature framework, or even developing a wrapper around other lighter and stabler libraries such as jQuery. or Prototype. @Anon: The truth is that ExtJs was poorly designed from the very beginning and there where no choice than complete redesign of some modules, of course with the price of sacrificing compatibility. I am in the same situation as you and I don’t know if I will ever upgrade. JavaScript is not Java or C++ where compiler does most of the job, you need very skilled developers to overpass the lack of tools. We also have some applications written in ExtJs2, that will never by upgraded. Rewriting a corporate applications from scratch every year because of unstable framework features is very expensive, and you will never get budget for that since the application is working fine in the eyes of the management. We are considering switching to a more mature framework, or even developing a wrapper around other lighter and stabler libraries such as jQuery. or Prototype.

]]> Thu, 26 May 2011 13:01 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:21889#date:13:01 Comment by Anon Fantastic framework and I love it but, such big changes in every release is killing many of us in large firms. Imagine going to the business and saying “hey we just put your application into production, now you need to pay for us to migrate it to a new extjs version”. Please do not pull me down with statements such as “use it only if you want to”.  Are we going to see this pattern in every major release going forward too? Fantastic framework and I love it but, such big changes in every release is killing many of us in large firms. Imagine going to the business and saying “hey we just put your application into production, now you need to pay for us to migrate it to a new extjs version”. Please do not pull me down with statements such as “use it only if you want to”.  Are we going to see this pattern in every major release going forward too?

]]> Mon, 23 May 2011 19:38 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:21748#date:19:38 Comment by Gajanan Borde Really excellent work ... Really excellent work ...

]]> Mon, 16 May 2011 08:58 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:21267#date:08:58 Comment by Luis Carlos Moreira da Costa Hi Brian @Excellent Tutorial Hi Brian
@Excellent Tutorial

]]> Sun, 15 May 2011 13:47 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:21206#date:13:47 Comment by JavascriptKickingAndScreaming I am in the throws of converting a fairly complex application from 3.3 to 4.0 and I’m seeing some odd behavior. All of my panels render fine by themselves after migration but when I try to load them all on a single page, they are all mixed up.  The first panel gets clobbered by the second panel and the third panel gets clobbered by the fourth, etc.  It looks like they are overwriting parts of each other. Fields from one panel end up on a different panel. A panel renders correctly and then a split second later, it’s a mess. Any suggestions? I am in the throws of converting a fairly complex application from 3.3 to 4.0 and I’m seeing some odd behavior. All of my panels render fine by themselves after migration but when I try to load them all on a single page, they are all mixed up.  The first panel gets clobbered by the second panel and the third panel gets clobbered by the fourth, etc.  It looks like they are overwriting parts of each other. Fields from one panel end up on a different panel. A panel renders correctly and then a split second later, it’s a mess.
Any suggestions?

]]> Fri, 13 May 2011 19:31 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:21103#date:19:31 Comment by George Jempty @Evan Trimboli: “What’s wrong with complimenting your colleagues?” If you’re colleagues, you can compliment them in private.  When you do so in public, without revealing that you are colleagues, it smacks of “self”-aggrandizement, where the “self” is Sencha From what I’ve seen of ExtJS4 and its documentation so far, if I were not working at a company that is already committed to using ExtJS, I would be recommending taking a serious look at alternatives.  I think Sencha needs some serious competition from another framework, because ever since Jack Slocum has left, I think your product has become sloppier and sloppier @Evan Trimboli: “What’s wrong with complimenting your colleagues?”

If you’re colleagues, you can compliment them in private.  When you do so in public, without revealing that you are colleagues, it smacks of “self”-aggrandizement, where the “self” is Sencha

From what I’ve seen of ExtJS4 and its documentation so far, if I were not working at a company that is already committed to using ExtJS, I would be recommending taking a serious look at alternatives.  I think Sencha needs some serious competition from another framework, because ever since Jack Slocum has left, I think your product has become sloppier and sloppier

]]> Fri, 06 May 2011 21:12 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20723#date:21:12 Comment by Gevik Hi Brian,  Excellent tutorial. You should start a new product line (video tutorials) about how to use ExtJS 4 Hi Brian,  Excellent tutorial. You should start a new product line (video tutorials) about how to use ExtJS 4 smile

]]> Wed, 04 May 2011 19:54 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20612#date:19:54 Comment by ibnesayeed Wonderful job Brian! I specially loved the videos. Wonderful job Brian! I specially loved the videos. grin

]]> Wed, 04 May 2011 16:11 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20599#date:16:11 Comment by Tobias Uhlig Hi Brian, just watched your first video and i like it. I think it will help a lot of community members with not too many custom ux, components and overrides to get a good start into the ext js 4 world Best regards Tobias Hi Brian,

just watched your first video and i like it.
I think it will help a lot of community members with not too many custom ux, components and overrides to get a good start into the ext js 4 world smile

Best regards
Tobias

]]> Tue, 03 May 2011 23:06 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20567#date:23:06 Comment by Jonathan Griffin Awesome work! Thanks for this migration path. It will help us immensely as we migrate our existing SaaS application and customer base to ExtJS 4. Awesome work! Thanks for this migration path. It will help us immensely as we migrate our existing SaaS application and customer base to ExtJS 4.

]]> Tue, 03 May 2011 15:23 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20529#date:15:23 Comment by Devnullable @Evan Nothing wrong with complimenting the colleague. My bad, I didn’t realize praise was directed to Brian. Nothing to see here, move along Sorry Mitch. @Evan Nothing wrong with complimenting the colleague. My bad, I didn’t realize praise was directed to Brian. Nothing to see here, move along smile Sorry Mitch.

]]> Tue, 03 May 2011 12:55 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20519#date:12:55 Comment by Cedric Your contact formular is not working so I post my message here. Hello,       Lots of your Ext JS 4 Demos are not working because the loading script is broken. I included some explanations below. I hope that it will be fixed soon. The bootstrap.js script is broken. This script tries to find its path by looking to the loaded scripts and finding itself. Then it extracts the path and load the “ext-all.js” script. But in the examples this scripts fails to find its path and tries to load the “undefinedext-all.js”. This is because the “bootstrap.js” script looks for a script whose path ends by “bootstrap.js” but in the deployed examples it ends with “bootstrap.js?sfgdata=+sfgRmluamFuX1R5cGU9amF2YV9zY3JpcHQmRmluamFuX0xhbmc9dGV4dC9qYXZhc2NyaXB0+q”. Best regards Cedric Finance Your contact formular is not working so I post my message here.

Hello,

      Lots of your Ext JS 4 Demos are not working because the loading script is broken. I included some explanations below.
I hope that it will be fixed soon.

The bootstrap.js script is broken. This script tries to find its path by looking to the loaded scripts and finding itself. Then it extracts the path and load the “ext-all.js” script. But in the examples this scripts fails to find its path and tries to load the “undefinedext-all.js”. This is because the “bootstrap.js” script looks for a script whose path ends by “bootstrap.js” but in the deployed examples it ends with “bootstrap.js?sfgdata=+sfgRmluamFuX1R5cGU9amF2YV9zY3JpcHQmRmluamFuX0xhbmc9dGV4dC9qYXZhc2NyaXB0+q”.

Best regards
Cedric Finance

]]> Tue, 03 May 2011 12:49 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20517#date:12:49 Comment by Loiane Groner Greak work Brian! Thank you! Greak work Brian! Thank you!

]]> Tue, 03 May 2011 11:56 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20515#date:11:56 Comment by Evan Trimboli @Devnullable I see nothing wrong with it. I work with Sencha as well and I think Brian has done a great job on this, he deserves the congratulations. What’s wrong with complimenting your colleagues? @Devnullable I see nothing wrong with it. I work with Sencha as well and I think Brian has done a great job on this, he deserves the congratulations.

What’s wrong with complimenting your colleagues?

]]> Tue, 03 May 2011 11:50 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20513#date:11:50 Comment by Andrew Peacock Great news: this is the type of thing that makes the Sencha offering much more than just the ExtJS code itself. Keep it up! Regards, Andy Great news: this is the type of thing that makes the Sencha offering much more than just the ExtJS code itself.

Keep it up!

Regards,
Andy

]]> Tue, 03 May 2011 08:58 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20507#date:08:58 Comment by FredricBerling Great work Brian. And you also have a great talent for making videos. Cudos! I understand we fellow Vikings meet in Split. See you there. Great work Brian. And you also have a great talent for making videos. Cudos!
I understand we fellow Vikings meet in Split. See you there.

]]> Tue, 03 May 2011 06:32 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20501#date:06:32 Comment by Grgur @devnullable Mitch wasn’t developing Ext JS 4 directly, right Mitch? He has done a huge amount of bug reporting and fixing to help Ext JS 4 get stable sooner for you to use it. I don’t think this is a good place for throwing rocks at anyone. Just remember, the choice of using this awesome open source framework is yours. You are always welcome to contribute in a constructive fashion. @devnullable Mitch wasn’t developing Ext JS 4 directly, right Mitch? He has done a huge amount of bug reporting and fixing to help Ext JS 4 get stable sooner for you to use it.
I don’t think this is a good place for throwing rocks at anyone. Just remember, the choice of using this awesome open source framework is yours. You are always welcome to contribute in a constructive fashion.

]]> Tue, 03 May 2011 05:54 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20499#date:05:54 Comment by Devnullable Does anyone else think it’s quite weird that Mitchell, who is working for Sencha, is commenting and praising their own work? Maybe it’s just me but I don’t find it very objective nor professional. Does anyone else think it’s quite weird that Mitchell, who is working for Sencha, is commenting and praising their own work? Maybe it’s just me but I don’t find it very objective nor professional.

]]> Tue, 03 May 2011 04:19 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20495#date:04:19 Comment by manduks rox this kind of efford for the comunity, updating 4 all, ExtJScellent! rox this kind of efford for the comunity, updating 4 all, ExtJScellent!

]]> Tue, 03 May 2011 03:46 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20493#date:03:46 Comment by Steffen Hiller That is the way to go! Push everyone to migrate to Ext 4. That is the way to go! Push everyone to migrate to Ext 4. smile

]]> Tue, 03 May 2011 01:54 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20488#date:01:54 Comment by Mitchell Simoens Great work and great write up! Wasn’t expecting the screencasts! Great work and great write up! Wasn’t expecting the screencasts!

]]> Mon, 02 May 2011 21:11 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20475#date:21:11 Comment by Grgur Awesome work Brian. Made my life easier. Awesome work Brian. Made my life easier.

]]> Mon, 02 May 2011 19:57 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20471#date:19:57 Comment by Florian Cargoet This migration pack must have been a lot of work! We appreciate the effort! This migration pack must have been a lot of work! We appreciate the effort!

]]> Mon, 02 May 2011 19:29 GMT http://www.sencha.com/blog//ext-js-3-to-4-migration#id:20469#date:19:29