there sth wrong here ?, is there sth else to do after app generation with Sencha Cmd 181 on MacOSX 10.6.8 (besides enabling Loader) so that not to receive that loading error. To reproduce it is very simple, just generate the app and then generate a model and then try to build that app.

I encountered the same problem. I am not 100% sure but this may have to do something where you put your models and views declarations. If you define them inside Ext.application everything seems to work ok but if you define them in the controller then it fails like you said.

For example you have controller Car, and model Car. If you define models: ['Car'] inside controller Car then Loader tries to load /app/controller/Car.js/model/Car.js which naturally fails. But if you define models: ['Car'] inside Ext.application then it should work.

Where we should define models and views? I would like to declare them in corresponding controller, not in Ext.application.

devnullable@, yes I know about all these things, my temporary solution is to take the namespace from the match[1]. I remember that in previous versions I have hadn't such issues, was just specifying app's path in Loader and everything worked, but with the new Sencha Cmd sth is working differently, which I don't know what yet.

bootstrap.js indeed has a entry for AppName.controller.Main and therefore hole class name is returned. If I comment out the controller entry in bootstrap.js the if statement returns false and the rest of the getPrefix function works as expected and returns only the AppName.

I don't know what is the purpose of the shown code and why it returns fully qualified path?

When store is defined in controller's stores property Ext.Loader fails to load store's JavaScript file because of incorrect path. When controller is named BookingSearch and store is named Bookings, Loader tries to load store's JavaScript file as app/controller/BookingSearch.js/store/Bookings.js