Collection of extensions from TuttleOFX: align, layers, lines, parallel, pattern, shrink, wuline

[mloskot]

There is a collection of interesting extensions (and their tests) in repo of TuttleOFX project which uses Boost.GIL:

https://github.com/tuttleofx/TuttleOFX/tree/develop/libraries/boostHack/boost/gil/extension/toolbox

Most of them have been authored by Tom Brinkman, a known author of GIL extensions.

I think it is a good idea to review some of them and port/add to current Toolbox extension.

[meshtag]

I am working on this. This might be a trivial question but I would like to confirm whether I am allowed to do small modifications in the code. For example : replacing typedef with using for aliases in order to improve compatibility with C++ 11.

[mloskot]

You're free to do anything the licence allows you to do.

GIL already can use C++14, see #526 (comment)

Yes, we prefer using aliases over typedef for aliases.

---

By the way, we also have an archive of old extensions https://github.com/boost-gil/gil-contributions-archive
and it may be good idea to review if any of the TuttleOFX's ones are present there, and pick the latest version.

[meshtag]

Alright, I will check that and submit a PR when I finish.

[mloskot]

Awesome, thanks!

[meshtag]

@mloskot, the format of test cases used by TuttleOFX is not in alignment with current practices followed by Boost Gil. I was thinking of developing some simple test cases of my own and adding them in a similar fashion to what I did in gil/test/core/image_processing/morphology.cpp.
Will that be fine?

[mloskot]

@meshtag They seem to be using Boost.Test while in GIL we use Boost.LightweightText
Although developing more/new cases on your/our own is certainly a good idea - the more tests the better - I'd suggest you to try port the TuttleOFX's tests to Boost.LWT format. It should be feasible - in GIL we used to use Boost.Test and we ported all our tests to Boost.LWT, a while ago.

[meshtag]

Okay, I will try to do that.