Backbone.js - file naming

[ghost]

Wouldn't be less confusing if there would be more precise rule of naming constructor>app.property>file chains?

Now there is:
collections/todos.js -> app.todos -> TodoList(); /// a mess, why not call the constructor Todos() or stay with TodoList for the property and file name - app.todoList and collections/todo-list.js?
models/todo.js -> app.Todo /// that's great!
views/todos.js -> app.TodoView /// a complete mess, the same file name as for the collection

Why not to have similar rule as it is in the Ember's app
edit_todo_view.js -> Todos.EditTodoView
todo.js -> Todos.Todo
todo_controller.js -> Todos.TodoController

Yes, that's a detail, but for novice as me it could help us much faster understand what's going on in the code without thinking "in which file there is the code I'm looking for" :). Especially the files with the same name "todos.js" are misleading.

Generally speaking I like the idea of including in a file's name info about the constructor's type. As it is in Ember's case showed above. Only models are single named:
todo.js
in Backbone case also collection
todos.js
but to others files we add suffixes:
todo-view.js, app-view.js

[addyosmani]

Would you like to put together a PR that addresses the concerns above? We would be happy to review it. Some of the naming conventions you see were carried over from a number of iterations updating the Todo app in the official Backbone repo and I'm sure there's room for improvement.

[ghost]

done