software – Matthew Petroff

Pannellum 2.0

Matthew Petroff — Sat, 23 Aug 2014 02:17:42 +0000

Two years in the making, I finally released Pannellum 2.0, which is a near complete rewrite. The renderer was replaced with raw WebGL, and multiresolution panorama support was added, along with a fallback CSS 3D renderer. Other additions include support for JSON configuration files, hotspots, tours, compass headings, CORS, partial panoramas, and cubic panoramas. I also put together a website for the viewer, registering pannellum.org. Unfortunately, there is still a dearth of documentation—something I need to work on. The below example demonstrates the multiresolution, hotspot, compass heading, and tour functionality using panoramas of the George Peabody Library and a JSON configuration file.

Kindle Weather Display

Matthew Petroff — Fri, 14 Sep 2012 20:10:11 +0000

Ever since I first learned about electronic paper, I’ve thought it would be perfect to display some sort of regularly updated, but not real-time, data such as the current date, an agenda, or the weather forecast. Unfortunately, e-paper displays have always cost more than I was willing to spend on such a project. However, with the price of Amazon’s cheapest Kindle recently dropped to $69, I decided e-paper displays were finally cheap enough for me to pursue such a project: an e-paper based weather forecast display.

The system consists of two parts, one running on the wall-mounted Kindle and one running on a server. The server fetches and processes weather data to create an image, and the Kindle downloads and displays it. While the Kindle is capable of handling both parts, I already had a server, and utilizing it saved me the time and hassle of setting up a build environment for the Kindle.

The server side of the system uses shell and Python scripts to convert weather forecast data into an image for the Kindle. The scripts first download and parse forecast data from NOAA via the National Digital Forecast Database XML/SOAP Service. After parsing the data, the data then needs to be converted into an image. This is accomplished by preprocessing a specially crafted SVG file to insert temperatures, forecast symbols, and days of the week. This SVG is then rendered as a PNG using rsvg-convert and converted to a grayscale, no transparency color space as required by the Kindle using pngcrush. Finally, it is copied to a public location on the web server.

Weather Icons Used for Forecasts

Before running anything on the Kindle, one must first jailbreak it and obtain shell access; this is left as an exercise for the reader. The Kindle portion of the system consists of a shell script that downloads the rendered image from the server, clears the screen twice to prevent ghosting, and then displays the image on the Kindle’s screen. On both the server and the Kindle, cron is used to execute the required scripts twice a day, with the server executing its scripts five minutes earlier than the Kindle to ensure a new image is ready. In addition, the Kindle requires an initialization script to disable the framework and power daemons to prevent the screen from being overwritten and to prevent the Kindle from going into sleep mode, which would disable the WiFi as well as cron, preventing any forecast updates. This initialization script was made easily accessible on power on of the Kindle using kite.

To create the icons, I started off with public domain icons from the Noun Project. Either using pieces of these icons or from scratch, I created icons for the weather conditions there were no icons available for and for those where there were no public domain versions. I am releasing the icons under the CC0 Public Domain Dedication and the source code for the scripts under the MIT License.

Files:
Weather Icons
Source: Archive, GitHub

Introducing Unofficial FontForge Windows Binaries

Matthew Petroff — Sun, 02 Oct 2011 20:17:22 +0000

I have recently been working on creating a font using FontForge, an open source font editor. Unfortunately, using FontForge on Windows is somewhat spotty, since it needs an X Server to run and is only officially distributed in source code form. While prior Windows builds exist, they are neither up-to-date nor user friendly. This prior work did, however, provide a good starting point for creating a new build (with the help of Google Translate and the Internet Archive’s Wayback Machine).

After downloading the development package and following the directions, I was eventually able to reproduce the older build it was designed for. Next, I updated the build environment, scripts, and patches to the latest versions and was able to produce a new build.

I had now addressed the issue of currency, but still had the problem of user friendliness. In its current state, the package could not be installed, was launched via a batch file, had no icon, and presented a visible X Server to the user. First, I addressed the issue of the batch file by writing a small program that runs without a window and runs the batch file without opening a command window. Next, I adjusted the settings used to start the X Server, so it would not be visible. Then was the icon issue. Using the Oxygen Project‘s FontForge icon and my prior work on Hugin‘s file and installer icons, I created icons and added them the the launch program I had just written. Finally, I created an installer based on Hugin’s installer.

In the end, I had an up-to-date version of FontForge that could be installed and run just like any other piece of software without any of the complexities exposed to the end user. With both issues resolved, I set about documenting and sharing my work. See the results for yourself: FontForge-Windows.