Ext 3 to 4 Migration

[brian.moeskau]

Just to clarify... the "preview" release is not intended as a full, ready-to-migrate release. We mentioned up front that there were missing components and that the docs weren't complete, etc. etc. The goal is simply to show what kinds of changes there are in the new architecture and gather feedback on what's there currently. Once the first feature-complete beta is available, along with the migration guide and compatibility layer that are currently being worked on, the migration effort will go much better.

[steffenk]

Hi Brian,

it would be cool if we would know when all components are in, or just a page where missing components are mentioned (stroke through if they are implemented)

I would like to test with already existing app to see which issues arise. I already tested (with components should be in pr2) and the viewport isn't rendered at all, difficult to say why, as there is no js error at all.

Maybe it's worth to throw exceptions if a component / class is called that is not present, would make the debug much easier.

[chrisvensko]

I know that Ext.reg has been deprecated, but it would be nice to update the exception to indicate which xtype is using Ext.reg.

reg: function(xtype, cls) {
  if (Ext.isDefined(window.console)) {
    console.warn('Using deprecated Ext.reg for the ' + xtype + ' xtype. Please use the alias configuration with the widget. namespace.');
  }
  Manager.setAlias(cls, "widget." + xtype); 
}

This would make it much easier to track down which xtypes are using the deprecated functionality during migration of an application.

[dajester2008]

The 'ref' config in Ext3 is not recognized in Ext4. In the API docs for Ext.AbstractComponent, under 'itemId', it gives a reference to see 'ref' and 'id'. I know this is nit-picking, but I only bring it up to get an idea whether or not this is actually planned for Ext4. This it is a very handy feature, and I would be very disappointed to see go away!

[msmolyak]

I am getting an error message described above: 'Using deprecated Ext.reg. Please use the alias configuration with the widget. namespace.' Is there any documentation on how to use aliases in Ext JS 4?

Thank you,

Michael

[Jehu]

I am getting an error message described above: 'Using deprecated Ext.reg. Please use the alias configuration with the widget. namespace.' Is there any documentation on how to use aliases in Ext JS 4?

Thank you,

Michael

Same question here.

[steffenk]

is #23 too far away?

[Jehu]

is #23 too far away?

Jo, sieht ganz so aus...
It seems...

[brian.moeskau]

I know that Ext.reg has been deprecated, but it would be nice to update the exception to indicate which xtype is using Ext.reg.

reg: function(xtype, cls) {
  if (Ext.isDefined(window.console)) {
    console.warn('Using deprecated Ext.reg for the ' + xtype + ' xtype. Please use the alias configuration with the widget. namespace.');
  }
  Manager.setAlias(cls, "widget." + xtype); 
}

This would make it much easier to track down which xtypes are using the deprecated functionality during migration of an application.

I've updated the (forthcoming) compatibility overrides for Ext.reg / preg (and their ComponentMgr counterparts) to include a more descriptive message that contains the type name being referenced. Thanks for the suggestion.

[brian.moeskau]

I am getting an error message described above: 'Using deprecated Ext.reg. Please use the alias configuration with the widget. namespace.' Is there any documentation on how to use aliases in Ext JS 4?

Thank you,

Michael

Lots of migration docs in the works, please be patient just a bit longer...

For this specific issue, it means to switch your class definition to something like this:

Ext.define('MyCustomClass', {
    extend: 'Ext.SomeOtherClass',
    alias: 'widget.mycustomclass', // <-- your custom xtype
    ...
});

Using this new pattern, Ext.reg('widget.mycustomclass', MyCustomClass) is no longer needed since it is now directly part of the class definition (hence the warning).

For a plugin replace 'widget.' with 'plugin.'