Base Distribution - Story #11968: Ext JS 4.0 integration
Run the current backend code with ExtJS4 in compatibility mode
#7 Updated by Sebastian Kurfuerst over 8 years ago
- Status changed from Accepted to Rejected
Regine has spent more than a week trying to get the Phoenix Backend run with Ext JS 4; and there are some considerable problems she discovered:
- as class handling has been completely changed, everything which uses xtypes needs to be adjusted.
- the ref-Option has been dropped completely, and instead, ComponentQuery has to be used. This completely breaks our way of connecting the Backend components, and we'd need some alternative solutions there. We'd especially have to look at a consistent naming convention for component instances there.
- ComponentQuery has quite some bugs, which makes it very hard to work with this in certain circumstances.
- CSS adjustments or adjustments to the generated markup is very tedious at some places; This means we cannot adjust the markup as much as we'd like it to do.
- Wait for bugfix releases; it's for us not yet usable.
- THEN, once a bugfix release is there, do NOT try to port the whole application at once, but instead rebuild the UI using Ext JS 4 components Top-Down.
However, as we cannot know when a bugfix release is given, we need to implement new features in current Ext JS 3, as we cannot have the migration block these tasks.
Regine said that Sandboxing (running ExtJS 3 and 4 in parallel) might be an option, which she will check when she has time.
She'll upload her current working state as zip file, so we can have a look at it.
Thanks Regine for your tremendous effort in this regard :-)