Hi again ;)
Just to make sure I understood it correctly: you didn't require the model in the store and in app.js at the same time, did you? If yes: you should require it only once,
either in the store
or in the app.js ;)
I would require the store in the app.js-file, like you did. The warning could only mean, that you have some typo in your store's name. When you write in your app.js
Code:
stores: ['Animals']
then the app will try to include the file
app/store/Animals.js. If this doesn't exist, it will throw an error. Note that there's an s in
stores: ['Animals'], but no s in your folder-structure: app/
store/Animals.js.
Are you sure that you did this correctly and don't have any typos? :-)
I think this Ext.create(...); isn't necessary...in your list, you can do
Code:
Ext.create('Ext.List', {
store: 'Animals',
[...]
});
when your store is called "Blue.store.Animals".
By the way, I think you don't need an id-property in your store...to access this store, you can easily do
Code:
var animalsStore = Ext.getStore('Animals');
To require the store in the model-file is not correct I think. So it was the right decision to remove that ;)
It's rather the other way round - the store need the model, because a store is a collection of models.
Above I wrote about that. It is definitely possible to do
Code:
store: '{STORENAME}'
If this fails, the error must be caused by a different issue.
In general: maybe you can watch in your console's network-tab (e.g. im Chrome or in Safari) what's going on and which files are loaded at which point of time. Probably this will bring you a step further :-)
Best regards,
Schildi