SenchaCmd 3.0.0.190 issues with Ext.Loader

I just tested with SenchaCmd 3.0.0.230 and Ext JS 4.1.3 and the issues still persist.:(

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.

Don

I cannot really post my app here (for obvious reasons).
I could in the ticket system - would that work?

Question,

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.

Quote:

---

Originally Posted by mysticav

Doesn't the bootstrap.js loads all the classes ?

---

If you check the generated bootstrap.js you can see that it starts "Ext.Loader.addClassPathMappings" so the purpose of it is to tell Ext.Loader which files to load.

Which means that Ext.Loader should not auto load classes

bootstrap tells Ext Loader which classes to load in one shot, isnt it ?

Quote:

---

Originally Posted by mysticav

Question,
... if you generate the app with Sencha Cmd, the Ext.Loader is disabled by default,.....

---

This has not been my experience. Although the docs say that "enabled" is false by default, I am finding that this is not the case and I have to explicitly turn it off...Furthermore, loader should be disabled for production all-classes.js but that is not the case either.

To my knowledge, during development you should be using loader, but once app is built (all-classes.js), it should not be used.

Quote:

---

Originally Posted by mysticav

Which means that Ext.Loader should not auto load classes

bootstrap tells Ext Loader which classes to load in one shot, isnt it ?

---

The "bootstrap" file contains information (also called "metadata") for the Loader that is used to convert class names like "MyApp.model.Foo" into URL's for dynamic loading. It also contains alias information which comes in to play when using Ext.widget or "xtype" config.

Loading is performed when explicitly requested (somewhat rare) or when there are "requires" or "uses" statements (typical).

I just tested this with SenchaCmd 3.0 GA (3.0.0.250) and with Ext JS 4.1.3.

- Problem #1 no longer occurs, so that is fixed.
- Problem #2 is still there though....

Can you run with the "-debug" switch and include the full log here? (Please include the exact command you run as well).