Success! Looks like we've fixed this one. According to our records the fix was applied for
a bug in our system
a recent build.
Sencha Premium Member
Sencha, what is the status of this? Forum is still showing "Wait! Looks like we don't have enough information to add this to bug database." although I have created a bug report in format you expect in this thread.
20 Oct 2012, 11:06 PM
I have looked into this and there appears to be some issue with using the models, views and stores configs within controllers and the generated bootstrap.js. The Jira id for this issue is SDKTOOLS-217. I did notice that this issue was resolved if you use requires instead of the previously mentioned configs.
Last edited by fmoseley; 21 Oct 2012 at 12:03 AM.
Reason: To include the Jira ID of the bug I filed.
, fmoseley@ thx, finally, 3 weeks that's a lot, too much to inspect such a minor bug. Regarding 'requires', yes I know, and the issue wasn't a blocker for us.
fmoseley, using "requires" is not a solution, is just an inconvenient alternative.
"requires" does not generate getters, also, does not instantiate the stores.
This is definitively a bug that has to be resolved ASAP, cause new people trying to adopt Cmd structure will end up bald!
This should be fixed in Sencha Cmd 3.0 GA (126.96.36.199). The issue had to do with how the metadata contained complete file names but the MVC namespace resolver was expecting path prefixes to define namespaces.
You will need to do a "sencha app refresh" to refresh the bootstrap.js file to get this to work.
Don, yes I saw in release notes and already tested, works, thx and thx for explanation also
Ext JS Premium Member
I am currently migrating our app to use Sencha Cmd (GA) + ExtJS 4.1.3.
I have this very same problem when I build my app with Cmd GA. All stores,views,models don't get loaded prior to the controller declaration. If I put a require statemnt in the controller, then it will load the class.
I have posted a thread about this in Sencha Cmd forum. Can anybody confirm that this is indeed fixed ?
yes, is fixed, just do app refresh.