Sencha Cmd v3.0.0.141 Build Process

Printable View

25 Sep 2012, 6:34 AM
jminnick

Sencha Cmd v3.0.0.141 Build Process

SDK: ExtJS 4.1.1a
Platform: Windows x64

I make it through the entire build process executing the following command:

Quote:

sencha app build

My pre-build index.html looks like so:

HTML Code:

<!DOCTYPE HTML> <html> <head> <meta charset="UTF-8"> <title>metrics_cmd_extjs</title> <link rel="stylesheet" href="resources/css/default/app.css"> <link rel="stylesheet" href="resources/css/default/metrics.css"> <link rel="stylesheet" type="text/css" href="ext/examples/ux/css/CheckHeader.css">   <script src="ext/ext-debug.js"></script> <script src="bootstrap.js"></script>  <script src="app/app.js"></script>  </head> <body> <div id="logo"></div> <div id="loadingapp">Please wait...</div> </body> </html>

My build index.html looks like this:

HTML Code:

<!DOCTYPE HTML> <html> <head> <meta charset="UTF-8"> <title>metrics_cmd_extjs</title> <link rel="stylesheet" href="resources/css/default/app.css"> <link rel="stylesheet" href="resources/css/default/metrics.css"> <script type="text/javascript" src="all-classes.js"></script> </head> <body> <div id="logo"></div> <div id="loadingapp">Please wait...</div> </body> </html>

I receive the following error in Chrome:

Quote:

Uncaught TypeError: Cannot call method 'define' of undefined

Obviously the error is happening in the [build] produced file "all-classes.js"

HTML Code:

Ext.define("Ext.data.ResultSet"......

It seems to me there is a file not being included in my build index.html that defines Ext. Am I missing something here?
25 Sep 2012, 7:21 AM
jminnick

If I run the skelaton app (the one produced by the generate command) through the build process this is what first appears in all-classes.js:

HTML Code:

var Ext=Ext||{};

When I run my app through the build process, this is what appears first in all-classes.js prior to Ext being set:

HTML Code:

Ext.define("Ext.data.ResultSet",{loaded:true,count:0,total:0,success:false,constructor:function(a){Ext.apply(this,a);this.totalRecords=this.total;if(a.count===undefined){this.count=this.records.length}}});
26 Sep 2012, 10:09 AM
chrisfarrell

index prep

Are we supposed to modify index.html prior to running a build?

For example, are we supposed to replace 'ext-debug.js' with 'ext-all.js' or something like that?
27 Sep 2012, 3:30 AM
jminnick

This did the trick:

http://www.sencha.com/forum/showthre...s-out-of-order
27 Sep 2012, 5:03 AM
jminnick

Quote:

Originally Posted by chrisfarrell

Are we supposed to modify index.html prior to running a build?

For example, are we supposed to replace 'ext-debug.js' with 'ext-all.js' or something like that?

Nope. I'm pretty sure the file included for your development work has no implications on the build process.
29 Sep 2012, 12:24 AM
dongryphon

Quote:

Originally Posted by chrisfarrell

Are we supposed to modify index.html prior to running a build?

For example, are we supposed to replace 'ext-debug.js' with 'ext-all.js' or something like that?

This is discussed in http://docs.sencha.com/ext-js/4-1/#!...and_app_single but in short, the index.html should not need to be edited unless you are dealing with 3rd party sources that don't work as simple add-ons to your classpath. See also http://www.sencha.com/forum/showthre...ndor-libraries

The compiler will process everything inside the "x-compile" section. It removes and does not parse the nested "x-bootstrap" section. If you need code that cannot be combined in to your "all-classes.js", this can be placed outside the "x-compile" block.

I hope that helps clarify this a bit. :)