Mateusz Loskot :: hacking on, working out, living up

Formal Review of IO and Toolbox extensions to Boost.GIL starts TOMORROW

30 Nov 2010 | mloskot

I am honoured to act as a Boost Review Manager for the proposed Boost.GIL.IO and Boost.GIL.Toolbox extensions. Today, I announced the review starting tomorrow:

According to the Boost Formal Review Schedule, review of Christian Henning’s extensions to the Boost Generic Image Library (Boost.GIL), it is:

starts on December 1st and lasts until December 10th, 2010.

What is it?

The Boost.GIL.IO extension provides an easy to use interface for reading and writing various image formats. It also includes a framework for adding new formats. The Boost.GIL.IO is indent to replace the current IO extension which is part of Boost for several years now.

The Boost.GIL.Toolbox provides new color spaces and other small code to ease programming with Boost.GIL.

The Boost.GIL as well as the proposed extensions are provided in form of a headers-only library Although, some image formats come with their format dependency, it is corresponding third-party libraries:

Getting the library

The latest version of both extensions can be downloaded as package or directly from the Subversion repository. The docs can built as usual with bjam and quickbook tools from within libs/gil/io_new/doc directory. The libs/gil/io_new/test/readme.txt provides a step by step guide to configuring, building and running the unit tests. (By the way, here are some more details on how we’ve managed to get the Boost.GIL tests building with Boost.Build and Boost.Build extensions

The is about 20MB due to its extensive collection of test images. They are part of the test suite to make sure that different variations of each image format is read and written correctly. Please, be aware no guarantee can be given that all formats in their all variants are completely supported.

Writing a review

If you feel the new IO and Toolbox are interesting extensions to the Boost.GIL library, then please submit your review to the developer list (preferably), or to the review manager.

Here are some questions you might want to answer in your review:

And finally, every review should answer this question:

Be sure to say this explicitly so that your other comments don’t obscure your overall opinion.

Fork me on GitHub