Use mixins for the actor system #52
Labels
No labels
0. Imported
1. Bug
1. Clean-up
1. Feature
1. Improvement
2. Deliverable
2. Epic
3. Duplicate
3. Invalid
3. Need investigation
4. Assets
4. Birb Core
4. Debug
4. Dependencies
4. Inputs
4. Lang
4. Scenes
4. Screen
4. World
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: epervier/epervier-old#52
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For the moment, the actor code is basically a mess.
Too much code is cramped up in a "basicActor" object, the actual actors (actor2D and actor3D) overrides many things.
Using mixins would allow us to make the actor code way easier to work with and understand.
It's also a necessary step to make the Actor2D and Actor3D objects childrens of Rect/Rect3D