-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Hi ! Do you think that your parser is compatible with ExtJS 5.x definitions ?
I'm currently using the latest 4.x definitions on top of ExtJS 5.1.1 and I have some obvious mismatches between the two API.
I would be happy to help improving the current groovy parser. What is the best way to do that ? A fork with pull requests ?
Moreover, I'm implementing some static factories (TypExt) on TOP of existing TS definitions. I have first extracted the "Config" options from your TS definitions (using a Perl script) into new interfaces (example: TypExt.panel.IPanelConfig is the Configuration of Ext.panel.IPanel). Then I have created some static factories for the instanciation of ExtJS objects.
This allows to do something like:
var panelConfig: TypExt.panel.IPanelConfig = { layout: "fit" };
var panel = TypExt.panel.Panel.create( panelConfig ) // panel is of type Ext.panel.IPanel
So we still deal with Interfaces definitions but we use "Type safe" factories returning objects typed with the appropriate interface. The "create" static method replace the usual "new" operator.
I don't have a factory for each existing class because I'm creating them manually but I guess this could be done in an automatic fashion by the Groovy script.
I can work on this also ;-)