Use code generation to improve component definition

Issue #14 resolved
Michael Ludwig
repo owner created an issue

There are multiple ways that this could be cool:

  • Component types are defined as interfaces only, with annotations to describe how data types are converted to properties
  • Component types could just declare fields, and assembly is generated to move data from properties and back as necessary. This would be the most straight forward because the actual underlying access would be the same, it'd just automate the access and onSet() method writing.
  • Could remove the need for unmanaged cached math objects everywhere

I might be able to tie this in with how Riven did mapped objects with buffers and ASM generation.

Comments (7)

  1. Log in to comment