My last Google Maps demo made me think a lot about data binding and Angular.JS, and I have actually created a pen with Google Maps powered by a pre-built Angular.js directive. so letвЂ™s get right to it, then:ДЄngular.module('ourApp', ).Angular.js, a powerful JavaScript framework developed by Google and designed for building web-apps, has seen a lot of adoption in the last few years. That is, a simple span element with an Angular binding expression, which will make more sense after we take a look at the Javascript part of our app. This line of code, which youвЂ™ll notice that we have placed in a separate HTML file, is all what our Component as a DOM element will include.

What is this element that weвЂ™ve never seen before? This, ladies and gents, is our component!Д«ut what does this component do, what do itвЂ™s responsibilities entail? Take a look at the code below: After that we see that we have a div managed by the controller MainCtrl, inside of which we have placed an HTML document which appears to have been named. Then, we notice that the whole body section of our document is made into an Angular app, named ourApp. ItвЂ™s mostly a standard structure of a main HTML document, where we notice at a first glance, that we have scripted two Javascript files, named index.js and eraDetail.js, both of which contain code parts that we will explain later on in more detail. The code snippet below shows us how the HTML part of our code would go: That means they are restricted 'E' and this is not optional. For more, letвЂ™s see them in action!Д¬omponents, even though they might be classified as a special case of directives, canвЂ™t be more than elements. directive(), cannot be a factory ponent()вЂs main role is to declare new HTML via a template or templateUrl, and itвЂ™s to be used as a creator of Components in a component-based architecture. component()? This method is a simple one that takes two arguments: the name of the Component as a string and the config object, which distinctly from. Nonetheless, it is quite easy to create and configure Components, and the basis for that is the method. The foundations for these codebases were laid way before components were added to our collective toolbox. Components didnвЂ™t become widespread until quite recently, and many of us are working with apps that have several years of history behind them. Creating and configuring a ComponentД®ven though people are talking about components a lot lately, most of the existing Angular code in the world is still not component-based. Nonetheless, if you correctly pick your battles and use Components as a feature of your app, it could make you all-powerful. Another example of when not to use Components would be when you need advanced directive definition options like priority, terminal, multi-element or when you want a directive that is triggered by an attribute or CSS class, rather than an element. These include: directives that rely on DOM manipulation and adding event listeners, since the compile and link functions are unavailable. There are, however, some cases when the usage of Components is not recommended. Components are optimized for the emerging application architecture that is heavily based on components, and using them will make the transition to Angular 2 much more seamless. They are under the wing of q number of programmers because they promote best practices and default pieces of code that make life easier for a lot of us. One of the most important ones is that components are easier than plain directives to get configured. LetвЂ™s see them one by one! 1.1 Advantages of ComponentsД¬omponents are recently gaining so much momentum for a number of reasons.

Like everything else, it has a number of advantages and also disadvantages. This way we have it remarkably easier to write an app in a way similar to using Web Components, or Angular 2вЂ™s style of application structure.

To put it simply, a directive is a component that works off of the inputs given and it can be used in any template anywhere and uses a simpler configuration which is suitable for a component-based application structure.Д«y definition, an AngularJS Component is a special kind of directive that uses a simpler configuration, suitable for a component-based application structure.

A directive is a feature all by itself, while a component is a piece of code that can be plugged into another body of code and be expected to behave as we want it to. Why are we, all of a sudden calling directives by the name components? TheyвЂ™re not the same thing, not exactly.

Angularjs code examples