14 Nov 2012 7:54 AM #1
Answered: Why doesn't Model config in a store automatically look in '/models/' directory?
Not sure I understand why in every other instance of referring to components in the MVC architecture of Sencha Touch 2, that in nearly every instance of referring to Store or a View, it by default looks in myapp/store and myapp/view, but when you're defining the model for a store, I have to set the config: 'myapp.model.mymodel', to tell it specifically to look in the Model directory.
Same reason that xtype or xclass configs in an item array doesn't, just not built that way. In the soon future Sencha Cmd will be smart enough to look at these configs for the build part.
16 Nov 2012 8:58 AM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
Same reason that xtype or xclass configs in an item array doesn't, just not built that way. In the soon future Sencha Cmd will be smart enough to look at these configs for the build part.Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
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 firstname.lastname@example.org
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.