In part one and part two of this series, we looked at how rivets handles data binding and then how to use rivets to show and hide elements on the page. In this post, things are going to get a little more interesting. We are going to cover how to consume JSON. Continue reading
I have been playing around with the Web Cryptography API a lot lately. My most recent post was about getRandomValues(). I wanted to take a moment to investigate two more methods: generateKey() and exportKey(). The generation of a good cryptographic key is fairly fundamental. I wrote up a short demo app, to demonstrate how the two functions work.
The code outputs to the console, so make sure to have Firebug open when you run the app. Also, keep in mind that the Web Cryptography API is not fully supported in every browser, so not all of the functions in this demo will work everywhere. I added in a description box for the crypto algorithms, so you can see the details of each one.
Have any questions? Feel free to drop a comment, below.
The W3C has been working on a Web Cryptography API for a while, now. The current version (11 December 2014) is their “Candidate Recommendation”. As such, I would not necessarily consider it fully ready for primetime but that does not mean that we can not play around with it a bit. I figured that today, we should take a check out getRandomValues().
According to MDN, “To guarantee enough performance, implementations are not using a truly random number generator, but they are using a pseudo-random number generator seeded with a value with enough entropy.” You do not want to use this method to generate encryption keys (especially since generateKey() is available within the same API). I think that this method is more foundational than anything. It is just meant to be part of the plumbing.
Have some thoughts? Drop a comment below.
These days, the lines between the web and the local environment can be very blurry. There is a web API called FileReader() that nicely adds to that blurriness. It lets you asynchronously read the contents of a file on the user’s computer. I am going to show you one way of using it.
So, what am I doing, here? There is an input tag that is set up to accept images. It triggers openFile() onChange. The openFile() function looks at the first (and only) file supplied and reads it as a data URL. The function then changes the innerHTML of the “TheImageContents” div to contain an img tag that uses the data URL as the source.
So, I have been working on a little side-hustle and I figured that I would share the most recent chunk of it. I needed a way of allowing a person to uniquely select a movie. You don’t want to just give the user a free-form box because of the 52 different ways you could input some movie titles. So, what do you do? I created a search box, to query IMDB by title. The API returns a single result, so I displayed it below the search box, as the user types.
I wouldn’t call this an “official” API, so I would be careful.