Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Entity (1) #14

Open
wants to merge 13 commits into
base: master
Choose a base branch
from
Open

Entity (1) #14

wants to merge 13 commits into from

Conversation

PtrMan
Copy link
Contributor

@PtrMan PtrMan commented Nov 21, 2018

A step toward Component based design.

Advantages:

  • drawing and logic are seperated (so we can run simulations without visualization)
  • behaviours are customizable and don't depend on the remaining functionality of the entity
  • ideally we need just one logic for rendering and simulation of different applications

Copy link
Member

@patham9 patham9 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the idea of Behavior being seperately from drawing. But why did you create a runtime-string-dispatched makeEntity method instead of just using the constructors?
Can you separate this into 2 PR's? The behavior one I would have accepted for sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants