JWPlayer is a fantastic video player for the web. One of the great features it provides is the ability to show thumbnail previews of the video as you slide along the toolbar timeline, much the same way that YouTube and the like allow.
Generating the thumbnail images is not quite so easy unless you have ffmpeg installed and know a bit about the command line options. I got a little frustrated myself having to come up the with the command line magic whenever I needed it, and so the JW Player thumbnail preview generator was born!
It’s a simple command line tool, written in PHP, that allows you to whip up the thumbnails and generate the required VTT file with a command as simple as:
php thumbnails.php -i "/input/video.mp4"
OK, so you still need to have ffmpeg installed on your machine – not much I can do about that one, sorry! – but at least generating the files is now much easier!
You can generate the individual thumbnails or have them coalesced into sprite sheet, and generate a random poster image. Full instructions are on my GitHub account; so go, fork, improve, and feel free to give any feedback.
Recently at work I found myself trawling through the PHP error log file and found that all the lines of text were starting to blur after a while. Thinking there had to be a better way over viewing the log file, and following on from my single-file opcache viewer gui, I decided to knock out something for viewing the error log file as well.
With this single-file error log gui it will only show the error once and then tell you how many times it appears in the log. It will allow you to narrow down your search of errors by being able to hide the different types or sort in different ways, and it will also allow you to search results based on particular file paths.
I’ve pushed the code up to my GitHub account, so please feel free to fork and improve and/or give feedback.
As I’m sure you know, you can create an ordered bullet point list but it has limitations. For example, if I wanted to have a table of contents so that the numbering goes 1, 1.1, 1.2, 1.2.1, 1.2.2, 1.2.3, 220.127.116.11 and so on then the standard ordered list just isn’t going to cut it. Oh, sure, you could reset the numbering on the sub-lists so that it uses roman numerals or something like that but to me that just doesn’t feel quite right…
Enter CSS counters!
Counters offer you a way to increment and decrement a value every time an element has the rule, and there doesn’t have to be one counter – you can have as many as you need,
So using counters can easily produce the correct kind of TOC list that we want. And here’s the jsFiddle to show you just how easy it is.
A while ago my door bell broke. So I did what any sensible person would; I decided that instead of buying a new one I would hook up an old bell I had to a Raspberry Pi and have the bell ring when someone pushed a button on my door. But then I though, “well, that’s a bit boring. My doorbell should tweet me, too!”
The long and the short of it is that I couldn’t get the mechanics of the bell ringer to work but had a lot of fun with the tweeting side of things because it involved my first shot at doing some Python code. And the really good news is that it’s ridiculously easy to accomplish.
The book seems squarely aimed at beginners in PHP and object orientated programming so lives up quite well to the “simple” aspect of the title. However, I wouldn’t really say “instant” because there are quite a few pages dedicated to setting up PHP and making sure it works with a simple “Hello world”. My preference would have been just to assume that someone that wants to know how to create bots probably already has PHP set up and has at least a passing familiarity with it. But as it seems to cater to real beginners I suppose it needs to hand-hold people through the setup.
The code is clear throughout and easy for anyone to understand and follow and by the end of it you’ll have something that will very basically scrape a web page. If you’re a beginner I’d imagine you’d be left with some sense of accomplishment and something pretty simple with which you should be able to tinker without getting too caught up with a tonne of code or complexity. However, if you are any kind of seasoned developer then you will probably find the book too light-weight as there are no advanced techniques are really discussed. But then, what would you expect with just around 60 pages in the book?
However, as I’ve said, the code is nice an clean, the book for what it is is well written, and the author discusses some good practices. Great for a beginner but probably not enough for a mid/seasoned developer.
Let me assure you, though, that by using Zend\Dom from the Zend Framework 2 library it’s actually a really simple task. In fact, I did it in around 20 lines of code.
So let’s start by looking at the code and then break it down a little more.
I use SVN for most of my projects at work and have diligently kept it up-to-date with the latest versions of the work copies. What happens when the working copy structure changes, as it did from 1.7.x to 1.8.x, is that Zend Studio gives error messages about the SVN connector client not being compatible. Annoying! However, if like me you’ve recently updated your SVN version to 1.8 and want Zend Studio to be compatible then it’s just a matter of a few easy steps for you to take.
A while ago I wrote a jquery plug-in that allows you to easily make selected elements all the same height. Well, it turns out that it could be a little better because it didn’t take in to consideration margins, padding and such. So here’s a slightly more robust version.
This will return that holds information about whether the opcache is turned on or not, whether it’s in a restart phase, the memory usage and hit statistics, and any files that have been cached along with hit and memory details. For example:
APC did have a GUI which was quite handy to see what had been cached, settings and memory usage but Zend OPcache doesn’t (currently as far as I could see) have anything similar.
It is possible to get information from looking at the output of phpinfo() which contains all of the key information.
However, I’ve just pushed the start of a GUI to GitHub. If you want to make changes and improvements then please feel free! It’s only had a very little amount of work done on it so far so is pretty raw.
I’ve used TinyMCE for a while – it’s an excellent WYSIWYG editor for web applications. However, the code editor in it is really simplistic. Enter CodeMagic, a plugin that allows you to replace the standard code editor with one that used the excellent CodeMirror library for syntax highlighting. So I started to use CodeMagic but found a number of issues with it. For example, it used CodeMirror 2 and not 3, had issues with using IE and the word wrapping functionality and the window resizing was never great. But with the joy of things being on GitHub and up for a bit of a forking, that’s exactly what I did.