A tool to generate notification images

[ckuethe]

Based on #565.

• Changed the camera-off-during-day background color to keep it consistent with the others.
• Made the error-see-logfile all use 72pt rather than 128+72pt because it was easier to code.
• Changed the image size to 959x719 so that they are easier to detect in case someone is using 960x720 captures.

Adding the generated output to this PR so that the output can be reviewed.

Thoughts?

[ckuethe]

Here's a question, and I don't have a strong opinion either way:

• do we want to "compile" the notification images as part of the build?
• do we want to include the images in the repo and regenerate them as necessary (probably rarely)?

[EricClaeys]

Wow Chris, you're good. If I mention that my house needs painting, will you be there this afternoon to do it?

Don't we want to delete the notification images from GitHub, and create them on the fly by having install.sh call the new script?

If you change the message of the Error image to this, you can use font size 110:
ERROR:\nSee \n/var/log/allsky.log\nfor information

I'd like to use this to make the "NoThumbnails.png" file used by allsky-website.
Can the function become a separate script that would be called the install scripts for allsky and allsky-website?
IM_SIZE, EXTS, and SW should be able to be optionally specified on the command line.

Message: No thumbnail, size: 200x167, text color: #fff600, no stroke. Ariel regular, 30pt. Background: #000000, with a 1px border of color #fff600. Only a .png file.

[EricClaeys]

I suggest we remove the images from GitHub and create them as part of the installation via the ~/allsky/install.sh script. This is assuming it doesn't take a really long time (more than a couple minutes?) to do so on a Pi 3.
I know we're thinking of INCLUDING the capture, keogram, and startrails programs so users don't need the whole development environment, but in the case of the Notification Images, they already need ImageMagick.

If we document how users can change the images, creating the images during installation would allow users to change them if, for example, they have a much larger or smaller sensor and want the Notification Images to match the sensor size.

[EricClaeys]

Just thinking, should the check for ImageMagick (and other necessary packages) go in the ~/allsky/install.sh script?

[ckuethe]

Given enough money, I could probably find someone come by to paint it. I don't think you'd like the price though.

This script is fast. A few seconds. We can delete the images from the repo after 0.8.5.

The build/install process should have a way to check for dependencies, eg. imagemagick, lighttpd, gcc, build-essential, ... but that's a different diff.

[ckuethe]

The thumbnail thing will take a little longer to figure out a good way to do that.

[EricClaeys]

Chris, can the font size for "Error" be 110? 128 is a little too wide and the first and last character a slightly cut off.

[EricClaeys]

Hmm, I thought we were going to use tabs in files, not spaces. This change converts the tabs to spaces.

[EricClaeys]

Closing since we implemented a modified version of this tool that has additional features.