Restructure the code (modular bash or python)

[ensonic]

With more and more coverage it is not easy to keep track of what is being converted already. Two proposals:

1. modularize the shell script. Here I would split it into a main script, a script with common conversion helpers and one script per mod (e.g. one script that converts all boat related textures). The main script will source the mod scripts and run them.
2. convert to python. Same kind of modularisation. Could use python-wand (http://docs.wand-py.org/en/0.4.4/) for imagemagick support.

WDYT? I could start this in my fork in a branch.

[sofar]

bash is already hard enough, I would actually prefer to go to golang instead, especially if we can get a nice simple cross platform UI that will work on windows, linux etc..

Python really sucks. Installing it and forcing players to pip install shit to get this to work is an insult to players. The target user can't even find cmd.exe, so we need to avoid as many dependencies as possible. Only golang would suffice, imho.

[ensonic]

go is fine for me (found e.g. https://github.com/gographics/imagick). FYI, there are ways to bundle pyhon modules into a standalone 'binary' (subpar), but people would still need the python runtime.
Ideally the converter is part of minetest so that people can simply 'import' a texturepack.

[rykerplayz]

How do I do this?

[sofar]

Do what?