We have numerous Ext JS 4 projects that are built using Sencha Cmd 4. Our build process generates an all-classes.js file containing all required JS to load our application. The resultant production html file is very simple:
Upgrading a simple Ext JS 4 application to Ext JS 5 / Cmd 5 and building the app using results in a production index.html file that looks something like:
Loading this index page results in loading of the app.json (!) which contains project paths that are not appropriate for (or should not even be deployed) to the production environment. The application does not work or load as expected and some classes are loaded dynamically even though they exist in the all-classes.js file (<script> tags are inserted into the index.html page to load these files). It seems that the "production" build is a confusing mix of dynamic and static content. The "all-classes.js" no longer contains all the required classes and an Ext.Boot is missing if we try and use the all-classes.js like we did in Ext JS 4. Everything works fine in development mode (dynamicaly loading resources via microloader) but we are unable to create a successful build for production use.
Unable to deploy Sencha Cmd 5 "production" build: needs documentation.
Code:
<!DOCTYPE HTML>
<html>
<head>
<link rel="stylesheet" href="resources/our-css-file.css">
<script type="text/javascript" src="all-classes.js"></script>
</head>
<body></body>
</html>
Upgrading a simple Ext JS 4 application to Ext JS 5 / Cmd 5 and building the app using results in a production index.html file that looks something like:
Code:
<script type="text/javascript">var Ext=Ext||{};Ext.manifest="app.json";Ext=Ext||{};
... heaps more code...
</script>
Loading this index page results in loading of the app.json (!) which contains project paths that are not appropriate for (or should not even be deployed) to the production environment. The application does not work or load as expected and some classes are loaded dynamically even though they exist in the all-classes.js file (<script> tags are inserted into the index.html page to load these files). It seems that the "production" build is a confusing mix of dynamic and static content. The "all-classes.js" no longer contains all the required classes and an Ext.Boot is missing if we try and use the all-classes.js like we did in Ext JS 4. Everything works fine in development mode (dynamicaly loading resources via microloader) but we are unable to create a successful build for production use.
No where in the documentation of Ext JS 5 / Cmd 5 is there a detailed description of production building and deployment of an Ext JS 5 application. What was a relatively simple process in Ext JS 4 / Cmd 4 is now confusing and totally different.
We are currently unable to continue using Ext JS 5 / Cmd 5 until a solution for production deployments is documented and implemented successfully for our test migration project.
Any help will be greatly appreciated.
Gerald
Unable to deploy Sencha Cmd 5 "production" build: needs documentation.
Aucun commentaire:
Enregistrer un commentaire