1 Nov 2012 4:40 AM #11
Issue still persists with SenchaCmd 188.8.131.52 and Ext JS 4.1.3
I just tested with SenchaCmd 184.108.40.206 and Ext JS 4.1.3 and the issues still persist.
1 Nov 2012 12:27 PM #12
How much of your app can you post here so that we can look at what might be causing the issue? Obviously, boiling it down is a good thing but so far we have not reproduced these symptoms so I think it may be triggered by something in your code. Perhaps an auto-dependency that is not being recognized.
1 Nov 2012 12:35 PM #13
I cannot really post my app here (for obvious reasons).
I could in the ticket system - would that work?
5 Nov 2012 6:28 PM #14
Why are you using Ext.Loader and bootstrap.js at the same time ?
Doesn't the bootstrap.js loads all the classes ?
As you can see, if you generate the app with Sencha Cmd, the Ext.Loader is disabled by default, because the bootstrap.js does the job.
5 Nov 2012 6:48 PM #15
5 Nov 2012 10:28 PM #16
Which means that Ext.Loader should not auto load classes
bootstrap tells Ext Loader which classes to load in one shot, isnt it ?
6 Nov 2012 5:48 AM #17
To my knowledge, during development you should be using loader, but once app is built (all-classes.js), it should not be used.
6 Nov 2012 10:16 PM #18
Loading is performed when explicitly requested (somewhat rare) or when there are "requires" or "uses" statements (typical).
9 Nov 2012 2:01 PM #19
I just tested this with SenchaCmd 3.0 GA (220.127.116.11) and with Ext JS 4.1.3.
- Problem #1 no longer occurs, so that is fixed.
- Problem #2 is still there though....
9 Nov 2012 2:41 PM #20
Can you run with the "-debug" switch and include the full log here? (Please include the exact command you run as well).