I’m using mostly the Qt Creator coding style, though with some exceptions (like using mMember instead of m_member). Also that document is outdated in terms of C++11 features like nullptr and range-based for loops (which they do use, and so does Tiled).
In general, the code should be quite consistent and new code should just try to fit in.
It would of course be good to mention this in a CONTRIBUTING.md file.
Thank you for your interest. Yes the desired outcome should be something similar to the tool on the video, we still don’t know how the workflow should look like since one should define the wang tiles before using the tool and then be able to use the tool either like a brush or like a bucket tool on a selected area.
And yes we can keep talking about the feature on the #1272 ticket.
Regarding the Wang tiles, indeed the first question is how will the user tell Tiled about the structure of his tiles, so that a Wang paint tool can know what combinations it can make. Also, a wang paint tool could probably either work entirely random or it could work similarly to the terrain brush.
I’d prefer to open a separate issue about supporting Wang Tiles, since issue #1272 is in itself really quite a bit simpler since it’s just about adding a more efficient way to fill rectangles and circles. It’s just something that could be made more interesting in combination with Wang Tiles.
Hi guys, I am a sophomore. I am very interested in this project. I have learned C++ and OpenGL(computer graph) so far. I have wrote some programs about algorithms and have no experience in particular application. Anyway, I will go through the code and try to contribute. By the way, Is it a good idea to learn some basic QT first?
Note however that while you’re free to take tasks from there, it merely represents my own priorities. While of course this represents the immediate things I’d like to see done for Tiled, you are free to choose your own things entirely.