Angular does not provide the "lego". Rather, it describes how the pieces are supposed to connect and how the pieces should be constructed.
Angular is all about connecting the html markup with javascript. Angular introduces custom html attributes (the default ones are prefixed ng but custom ones can be created as well) which the framework wires together (2-way binding) with the model (ng-model) described in the $scope of that element. Angular has a elaborate inheritance hierarchy of html elements where html elements “inherit” the $scope of its parent element unless it uses a different ng-model. All the built-in Angular attributes are *behaviors* rather than *components*. You could probably put those in two categories: 1. Those which extend default HTML behavior (i.e. ng-show, ng-mousedown, ng-src, etc.) 2. "functional" attributes like ng-repeat, ng-switch on, etc. The first category binds javascript objects and properties with html elements, while the second category actually changes the html structure. Of course custom components can be (and should be) created and that’s what AngularUI[1] is all about, but it’s not part of the core framework. Does this make more sense? HTH, Harbs [1] http://angular-ui.github.io/ On Jul 10, 2014, at 8:57 AM, Alex Harui <aha...@adobe.com> wrote: > I'm still trying to understand why you don't think there is "lego" in > Angular.
