[chm]

This is actually great for someone learning Angular. It's just a different way of presenting the exact same material. I was completely dumbfounded at first when learning Angular. This would have helped.

I very much suggest everyone interested in Angular development to read what the guys at MeanJS.org[1] have to say about structuring modules. It helps me think about my app a lot better. The structure could be cleaned up a bit though (e.g. module A can use module B's filters at run-time, this is a bad thing IMO. There should be global and local filters).

[1]:http://meanjs.org/docs.html#angularjs-modules

[jradd]

I just want to let you know that I really appreciate your empathetic suggestions for those [like me] trying to learn intermediary aspects of AngularJS; of which I am going to relate to—the learning of how to walk——and then applying that knowledge to break atmo and venture into the stars. :)

TLDR; THANK YOU (Intermediary AngularJS learning–curve is friggin hard.)

[chm]

You're welcome. I am an AngularJS neophyte as well... but the mental picture I have of the framework is definitely clearer than it was two months ago!

[grosbisou]

Very nice! I am doing a project with angularjs right now to learn and it's really interesting. If you have other resources that explain how to do things the right way it would be welcome.

[larakerns]

I would go with writing directives over using global scope in general, though it's more time consuming to me.

[chm]

But I need some filters to be "global" and some to be "local". I need to call some in different modules, while some are useful only in one particular module.

I haven't found out how to do this yet. Not fixing it until it breaks, even if that means I'll have to re-write parts of the app.