Echo JS 0.11.0

<~>
paprikka 4056 days ago. link 2 points ▲ ▼
I was working on a grunt.js based application scaffolding tool following very similar concepts. There are two things I find rather problematic: 
1. handling more sophisticated modules (eg. Users module, containing $resources, several CRUD based controllers).
2. packaging SASS modules along with JADE/HTML templates and CoffeeScript/JS code.

The structure I came up with looks like:
assets (static stuff)
- public (build)
- src (actual app source)
-- common (contains js / .scss / .jade module agnostic source, like layout, typography)
-- users
---- services
---- controllers
---- directives
---- partials
---- styles (sass modules)
---- users.coffee (main module loading directives, controllers inside subfolders) 
- vendor (3rd party packages from Bower)

We could replace subfolders with hungarian-style naming as you did, I'd say it's a matter of personal preference.

I think a mixed approach should scale a little bit better.
An example of what I'm trying to achieve: https://github.com/paprikka/angular-skeleton-redux (the architecture is still work in progress, going to move a new version to a different repo)

Replies

marcorinck 4055 days ago. link 1 point ▲ ▼
yes, it really looks very similar.

We discussed something like this too, but in the end, we didn't have a feature that was big enough to justify the extra bit of complexity that the additional folders are. In fact, if a feature gets big enough, I first would think about how to cut it into smaller pieces. 

But in the end, thats a sense of taste.