-
Notifications
You must be signed in to change notification settings - Fork 29
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
Roadmap #1 #9
Comments
ekiefl
added a commit
that referenced
this issue
May 20, 2021
ball.py. Base classes are in objects/__init__.py. Addresses one of the milestones in #9
|
|
Merged
Mission accomplished |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The state of the code is becoming more and more complex, and I need to simplify the design for my sanity. At the same time, I have written so many classes and functions that docs have become important, even if for no other reason than for my own personal use. Here are a couple of things I need to do, and I'm pretty sure it should be in this order.
objects
is getting huge, and I think it would be better to move object type, e.g.Ball
along with its child classesBallRender
,BallHistory
, etc., into their own submodules.engine
may be better calledsystem
, and all algorithm stuff may be best put in ashot_algorithm
submodule that contains a class that can select whichever algorithm to use based on keyword.The text was updated successfully, but these errors were encountered: