Nikon Coolpix P7000
The 10-megapixel Nikon P7000 is a premium compact with 7.1x optical zoom, Vibration Reduction (VR), manual exposure control and a 3-inch, 920,000-dot LCD screen.
The 10-megapixel Nikon P7000 is a premium compact with 7.1x optical zoom, Vibration Reduction (VR), manual exposure control and a 3-inch, 920,000-dot LCD screen.
It can generate an image with a random text made of hexadecimal digits.
The class stores the text in a session variable for posterior verification.
The image is served as the current script output in PNG format.
It provides several functions for retrieving information about files like the file size, last modified time, file or directory type and real path.
These functions work with files with size larger than 2TB (more than 31 bits) by using operating system calls or external commands to retrieve the requested file information.
It supports either Linux, BSD and Windows.
It takes a text string with words encoded using UTF-8 and converts it into stems strings like the soundex algorithm does, so similar sounding words result in the same word.
The class supports both English and Cyrillic words.
It can open a given PDF file and regenerate it inserting special JavaScript code to make it open the print dialog when it is opened.
The altered PDF file may be saved to a given file or displayed as the current script output.
If you’ve been using (or will be using) the uuid and imagick extensions for PHP, you might be able to save yourself a lot of headache by reading this new post from Lars Strojny about his segfault woes.
Ran into a bug yesterday, where http://pecl.php.net/uuid in combination with http://pecl.php.net/imagick yielded a segfault when using uuid_create().
After trying to trace it down with a backtrace and cachegrind results, he (and Mikko & Pierre) found that both extensions were built against the libuuid.so.1 file. While that wasn’t the issue directly, they did find a work-around that helped the issue – renaming some ini files so uuid was loaded first.
In this new post to his blog Till Klampaeckel talks about two tools for front-end interface testing – Selenium and Saucelenium – and how he used the latter in his application testing.
Selenium and Saucelenium have the same root – in fact Saucelenium is a Selenium fork. While the Selenium project seems to focus on 2.x currently, stable 1.x development seems to really happen at Saucelabs. That is if you call a commit from January 22nd of this year active development.
He talks about the installation process (guided by the README from his fork) and the tool he had to install to get it to work for him – xserver-xorg. He includes a sample test to give you an idea of what can be done with the testing tool. It loads the page imitating Chrome and looks for certain text on two different pages as well as check one of the links.