Rework directory structure

[jhnns]

alamid currently forces a rails-like directory structure like

• models
• views
• pages

I've following tj's components now for a while and I agree that it's better to think in self-contained components (like tj points out here). So instead of dividing our classes by their type (model, views, pages), you'd divide them by their domain (typically named after the model):

• user/
  • User.class.js
  • UserProfile.class.js
  • UserProfile.html
  • UserList.class.js
• event/
  • Event.class.js
  • EventView.class.js
  • EventView.html
  • EventList.class.js
• location/
  • Location.class.js
  • LocationView.class.js
  • LocationView.html
• pages/
  • home/
  • HomePage.class.js
  • HomePage.html
  • events/
  • EventsPage.class.js
  • EventsPage.html

As you notice, Pages are very app-specific and therefore in their one pages folder.

This structure allows you, to write components that are used across several apps which is a common use-case I think. Imagine an application that has a frontend and an admin interface (like Wordpress). These two applications share some components, but you usually wouldn't implement both interfaces into the same application.

[meaku]

I don't think that components always have their own model. Many components share a model or might not have a model at all.

[jhnns]

That's true, but I didn't meant that every component needs a model.

[meaku]

We should decide about this issue before we freeze the API. This would be a big change imho.

[jhnns]

Yep, this needs to be discussed sync.

[jhnns]

There's currently also no place to but base-stuff like base-pages or base-services.