Consider to moving to Chromium

[jvolker]

Following up from https://github.com/OpenframeProject/Openframe/issues/44

@jmwohl:

[…] the core of the idea behind Openframe is that an artwork format extension can define exactly how artworks are displayed, I'd like to avoid using Chromium for formats that don't specifically require it. I understand the additional desire to have attribution displayed, but for now I think that requirement is secondary and doesn't warrant reliance on Chromium.

I do understand that Chromium has more of overhead compared to glslViewer and think it makes sense to stick to glslViewer for performance reasons. Though, I do think using Chromium would not break with the core idea behind Openframe. It would still be possible to define exactly how the artwork is being displayed.

I would see two advantages to this:

• support for GIF images: we wouldn't need a separate GIF extension. Having two extensions for images I would find somewhat unintuitive.
• support for captions: this would allow displaying author and name of the artwork as an overlay https://github.com/OpenframeProject/Openframe/issues/59

Maybe moving to LXDE-pi (https://github.com/OpenframeProject/Openframe-Website/issues/14) would bring some performance improvements with Chromium and justify moving away from glslViewer?

[jvolker]

Another reason to consider moving away from glslViewer is that it doesn't seem to handle large images (maxing out GPU memory?). More on this here: #6