Browsed by
Category: JavaScript

AngularJS Directive and Service for HTML5 Audio

AngularJS Directive and Service for HTML5 Audio

While working on a project with my good friend we had the need to play audio playlists for a website. Originally we were using jPlayer but this seemed like overkill for what we needed. Plus, with our site built on the AngularJS framework, I wanted a more modular component like the rest of our code.

As such, I decided to create an AngularJS implementation to handle HTML5 audio – a service for handling the audio functionality that is needed by our website, and a directive for placing the player on our page and allowing user interaction.

The first thing to do was to set up our directive so we can start to see our player elements on the page.
All we need initially is pretty much an empty directive:

This just gives us a clean slate to start adding in our functionality. As you can see we’ve set a templateUrl, so we now need to create the html for that:

This adds now functionality as it stands, but now we can insert the directive into our page and, using the glyphicons provided by Bootstrap, see basically what an audio player should look like.

Now we’re going to need a service so that we can actually have our player do something. First, we need to create the service so we can start adding things to it:

This just gives us a service that we can inject into our directive called ‘PlayerService’, but as it stands it doesn’t do anything. We’re going to want our service to return an object, that way we can set it on the scope of our directive so it can be more easily called from the template. We also need to add the properties and functions to give us some basic functionality – we’ll start with the basics such as playing, pausing and setting the tracks.

On the service create an object (I’ve just called it myPlayer in the example) and have the service return this object.
In this object create variables for the current list of tracks (for the demo I’ve filled this with some freely available tracks from another website), the current index that we’re playing and a value for whether or not the player is currently paused. We’ll need a reference to the audio object so that it can be used, so add that too.
We’re also going to need functions for playing and pausing audio.

Our play and pause functions are very basic – the play function simply plays the currently set audio, while the pause function will simply pause or play the audio element based on the variable we added:

I’ve set the source of the audio player to the current track (defaulting to the first) in the tracklist for this example. How you set the playlist and which song to play is up to you, based on what you’re wanting to achieve. For example, in my own work I’ve created a playlist with the option to play any track on the playlist – as such this takes in the playlist and the index of the track as parameters, and I set the source in the play function.

As you can see from this code, we’ve also injected an AudioFactory into our service, so we need to create that:

The factory is very basic, simply creating and returning a HTML audio element, but doing this not only gives us an easy way of calling functions on this element from our service, it also makes it much easier to implement unit tests on our code (I’ll cover this in a later post).

Now we can inject this service into our directive and add a reference to it on the scope, so our directive will now look like this:

Now we’ve done that we can add calls to the service in our directive’s template, so your play and pause buttons will look like this:

If you run this, you can now see that clicking these buttons will do as advertised – playing when you click play, and click pause will pause the audio.

This doesn’t give users much control over the audio, so let’s add the ability to skip forwards and backwards.
To do this, we first need to add two more functions to our service, the next and previous functions. These will simply set the source of the audio accordingly, and call the play function to start the track:

Now we need to add a way to call these from our directive the same way we did with play and pause. From the original template we already have the buttons in place, we just need to add the click handlers to call the functions, making the template now look like this:

And that’s all there is to it. These can now be easily re-used across projects, and (I think, at least) are nice and clean to read and use, and can be easily extended to add extra functionality or be tailored to your needs.
It’s quite easy from here to handle other aspects you might be interested in – such as displaying and interacting with a playlist, handling volume controls, a seek bar for the current track etc.

A working Plunk of the code can be found here:

As always, feel free to let me know if I’ve gotten anything wrong or of any way to improve things!

AngularJS Directive with Chart.js

AngularJS Directive with Chart.js

As part of a project I’m working on with my good friend Ryan we found a need to be able to easily create some charts to display some metrics to our users. As we’re using AngularJS on our site, the logical step was to create a reusable directive that would allow us to easily hook up charts wherever we needed them – and this is what I’m going to walk through in this post.

I’ll assume you know the basics of setting up an Angular app so I won’t cover that here, and I’ve gone with the very unique name ‘app’ for mine. Download Chart.js and add a reference on your site – or reference the hosted script like I’ve done for this demo (though I’d never recommend this approach for anything that actually goes live!).
So the first step is to create your controller as this is where we’ll be setting the values and options your chart uses, as well as the specified chart type. For the purpose of this demo I’ve borrowed the line chart data and options from the documentation section of the Chart.js website.
I’ve added variables for ChartType, ChartData and ChartOptions on to the controller and initialised with the borrowed values, so my controller looks like this:

Now we have a controller where we can dictate the type of chart we want to load, along with the data and options to be used. Obviously in this sample I’ve hard coded the values which isn’t very useful – ideally (and this is what I’ve done for our project) these values would be retrieved from an Angular service.

The next thing we need to do is to create a directive that makes use of these values. The main things we need here are the template that will be used, the link function for the code to generate the chart, and the scope so we can isolate the values required for the charts.
Given how simple it is to create a chart using Chart.js – it’s just a canvas element – I didn’t see the need to separate this out into a separate HTML file to be used, which would be my usual approach for anything more complex.
The link function needs to find the chart on the page, and determine what chart to create based on the ChartType variable I set on the controller. Using this it then creates the specified chart on the canvas.
Following this, I know have the following directive:

As you can see I’ve used a switch statement on the ChartType in order to call the appropriate method for creating a chart. This is the part of the sample I’m not overly happy with, but I can’t find a better way. Ideally, it would be a single method call to Chart.js that takes in the chart type as a parameter, but instead there are separate methods for each different type – hence the switch statement.

That’s all that’s required! The directive can now be used to create a chart on your page easily, just modify the controller to set the scope variables and your chart will be created as you specify.

My index.html page to use the directive looks like this:

As always, happy to take input and learn if there’s a way I can improve any of this!
And if you’re interested in taking a look at my full code, it can be found on GitHub here.