Coding Style about curaengine

[daid]

Hi Bernard.

You are perfect right. This structure grew into place like this. At the start is was easy and quick to develop right this. But now the engine has grown quite a bit and that did not make it faster to compile or really clean.

I agree with the documentation in header files. I'll clean it up a bit later ok? I understand how the code fits together so it's easier for me to split up properly.

Note for a general structure and idea, be sure to read the readme, this explains a few basic things. (I hate doxygen, on my previous job they managed to make the comments into an unreadable mess with it) But the code really needs some extra comments.

(As for "inline" this is not always respected by GCC. See https://www.kernel.org/doc/local/inline.html The "vector" functions need to be in a header like this to be properly inlined, but the rest should be in cpp files)

But first, I have to do some Cura GUI bugfixing.

[daid]

Totally refactored the code to fix the coding style. It's on the refactor branch right now: https://github.com/Ultimaker/CuraEngine/tree/refactoring