I thought it was time for me to move on and see what I can achieve if I use the EAK for my further projects. first I wasn’t able to start the plain EAK from it’s current status on my Windows7 machine, so I grabbed the
ember-app-kit-todos GitHub project and with this code, I was finally able to run the application.
but, as I checked out the structure of this repository, it seems to me that it’s different to what is suggested in the “main/core” EAK.
In the “main/core” EAK all files are structured to live in folders which represent their “type” as the following folder/code structure is given:
# adapters # components # controllers # helpers # models # routes # styles # templates # utils # views app.js index.html router.js
while in the
ember-app-kit-todos example, the structure is like this:
# adapters # components # helpers # models # styles # todos // <-- Routes/Controllers/Templates all in one place, more namespace-like + # active + route.js # completed + route.js # index + route.js template.hbs // <-- resolves to 'todos/index.hbs' ??? # item-controller + controller.js // <-- resolves to 'TodosItemController' ??? controller.js // <-- resolves to 'TodosController' (?) route.js // <-- resolves to 'TodosRoute' (?) template.hbs // <-- resolves to 'todos.hbs' ??? # utils # views app.js index.html router.js
so, what’s suggested, common/best practice on code structure when using EAK? are all
template.hbs files converted to
#folderName#.hbs? so why do components still reside within their own
components folder? what about views/utils/models etc?
is anybody currently working with EAK and the latest stable version of Ember (v 1.4.0 at the time of writing) and is willing to give me some advice?