Class rewriting and reimplementation

[Nebula-Developer]

There's a few classes and interfaces within Yoru Engine that are due for a rewrite both for efficiency and clearness. The primary ones are both Element and Transform - we need to consider whether parents under Element will be an interface in the case that some elements handle children differently. Additionally, we may make Transform values fall either under an interface, or directly in the Element class.

Positional input will be further discussed in the future. I plan to partially match Yoru Engine's input with the likes of what would be seen in a web browser, but I'm not sure what picking implementation will be implemented.

[Nebula-Developer]

A few notable changes that are going to be made:

• AddChild will be added to Application, pointing to its Element.AddChild
• Mouse picking will be implemented, creating a new virtual method for Elements to handle rendering the positional contact area
• Additional platform information will be passed, for the likes of platform-specific elements (like touch-controls for mobile) or just generally understanding the applications environmental context