Author: s20

– add some bookkeeping to the abstract container
– use a different way to write memeber variable comments (sic)

The book keeping in this case means calculating the absolute size of the children inside a container as well as recalculating it when adding/removing children.

– do more refactoring
– add a first concrete implementation (a “button” that does nothing but draw its background colour)
– change the interface (and implementation) of the abstract container class, use smart pointers instead of references so that we can actually use abstract classes

That basically says it all, that new button does not do much yet besides existing.

more namespace refactoring

No functional changes today!

add very basic UI logic, nothing works, all WiP and not integrated into the renderer at all

This adds a whole lot of base logic for the UI, the next big step in the evolution of OLives, as so far the entirety of user input is done through hot keys. While it is very exciting to keep pressing ‘o’ after switching to the right game mode, it also does not work as a long-term solution.
This commit adds logic for widgets, a container class which is also a widget, but can contain other widgets and a whole chunk of base logic about calculating sizes and positions.
Widgets can be relatively (in relation to their parent) or absolutely (in pixels) sized.
They also can already create model data (vertices), using the same type of ModelData structure as is used for the elements that can be rendered, meaning the models, walls, tiles and build markers.
As it also says, this logic is doing nothing except that it can get compiled and linked, it is as of yet completely unused.

split up inline getter/setters

Moves the logic for them from headers to the respective .cpp files.

add a further check (for walls in the way) for the building marker start points

Some cases were not covered yet, now they are!