Google Code-in

All the UI in Terasology is done using our own system called NUI.

This task serves as one of the first steps towards getting that system extracted to it's own library as per this issue.

One of the issues on the road towards that goal is a sometimes too tight integration between NUI and the rest of the codebase. Some classes, which are technically considered a part of NUI are used all throughout the codebase even for UI-unrelated things, while others might be almost UI-exclusive yet not part of the NUI. There are also classes made part of the NUI that make complete sense to be within the NUI in the context of Terasology, but which might be near useless for anything else. Your task is to identify some of such cases, and preferably also suggest the solution for separating them.

Acceptance criteria

• A list of your findings is posted as a comment to this issue.