Twitter Bootstrap Navbar as AngularJS Component
You all know Twitter Bootstrap, don’t you? It’s the awesome library to make your web application looks pretty good without spending many hours on CSS. We are using Bootstrap based design in our current project that also uses AngularJS and as we are planning to have many new pages, we decided that’s the earlier we introduce some components to our UI the better. And, what shouldn’t be a surprise, navigation bar natually became the first candidate.
So in this post I am going to show how externalize Twitter Bootstrap Navbar into a separate, flexible AngularJS component. All source code is available in my GitHub repository , so everything should be easy to follow and repeat.
To start from the basics, I’ve prepared three pages that use the same navigation bar. These pages will soon become our super simple web application using AngularJS:
Next step will be adding AngularJS and converting three pages into one small application. This is done in this commit. And after that we are ready to start working on our Navbar component.
On each page we have very similar html fragment rendering navbar element.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
The only difference is in where class active which highlights link is located. And every time we see such repetition, our DRY detector should start ringing and don’t stop until we do something about it.
For a start, we will move this code fragment into a AngularJS directive. At first, it will be only a “dumb” piece of code that just renders the same html in different places. All html from the listing above is now located in the components/bootstrapNavbar.html file.
Next thing we need is a directive declaration in JS file:
1 2 3 4 5 6 7 8 9
What happens here:
we declare directive, please keep in mind that name of directive you use in the code will be boostrap-navbar, camelCase is transformed into – character.
restrict: E – means that directive is used as an element, there are other options: C-class, A-attribute, more on docs
replace: true – means that markup from template will completely replace directive element in the page markup
transclude: true – what it means… you better tell me, I am not able to describe it more vaguely that it is done in the docs ;)
templateUrl – file where we store our template content
After that we should replace navbar html markup on every page with something like:
Now it’s high time to test it. Unfortunately there is one problem. Security policy does not allow browser to execute XHR(Ajax) calls from html file stored on our disk. So we have to setup lightweight httpServer to serve our files to browser. You can do it using Jetty or anything similar. I tried one from Python and it worked without issues. So basically navigate to directory where all files are stored, execute:
and then open your browser using address http://localhost:9000/home.html. You should see the same page as before, but now it is using our directive.
So we have our first directive, yay! But its IQ is not that high. If you navigate to Second and Third Page, you will notice that it always renders link to Home Page as active, which is not exactly true for all pages. And in this paragraph we will try to make it smarter.
At first, let’s add attribute current-tab to our directive usages:
Passed value must be the same as link name in the navbar, so in our example app it should be either: Home, Second or Third.
Next step is to prepare our template file for easy modification. Because we will use jQuery selectors to find link to activate, we will remove active class and also add an id attribute to ul element to make it easier to locate with selector:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Core logic Now the last thing we have to do is some jQuery selector magic with little addition of AngularJS magic :)
Angular directives have function compile which allows to alter directive template markup, so we will use it here. What this function receives is value of parameters defined on the component usage in our pages, so basically we have an access to all attributes that are declared where our navbar component is used, specifically our current-tab attribute (again transformed to currentTab inside JS file). So when we know which link should be highlighted, jQuery selectors come to do the actual job:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
So what we do here:
define compile function that has passed two things, element on which it is called (template markup in our case) and attrs, an object with all attributes declared where our directive was used.
select all list items from #navigation-tabs node
find all links there, it will be only one
if text content of link is equal to currentTab attribute we know that this is the link to highlight, so we simply add proper CSS class there
It’s the simplest working solution. Of course we could add some error checking, but I wanted to show easy to follow approach to introducing flexible components to AngularJS applications.
In this post I tried to show how with a few simple steps we could apply DRY rule to our html markup in AngularJS application. And as your application grow, you will probably find more and more places where html is duplicated making it a good candidate to convert it into component directive.