-
30 Nov 2011 9:25 AM #1
How should we use all-classes.js
How should we use all-classes.js
I've gotten everything running with app-all.js. However as I come across bugs, I'd like to use the non-minified all-classes.js but, as I understand it, all-classes does not contain app.js and so can't be run on its own. So how are we supposed to use it? By including all-classes in the html? By modifying app.js to look for all-classes?
-
30 Nov 2011 9:51 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,714
- Vote Rating
- 436
When I need to check on something, I will usually just go back to loading app.js and letting everything autoload like before doing the build.
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
30 Nov 2011 1:12 PM #3
I have a bug that appears only in app-all and not in app.js (probably because I'm still not building correctly).
However, I came up with my own solution to my problem. Inside the .jsb3 file I set compress: false on the app-all.js target like this:
Code:{ "name": "Application - Production", "target": "app-all.js", "compress": false, "files": [ { "path": "", "name": "all-classes.js" }, { "path": "", "name": "app.js" } ] }
Thank you for reporting this bug. We will make it our priority to review this report.


Reply With Quote