-
Notifications
You must be signed in to change notification settings - Fork 5
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
More compact source code #11
Comments
Refactoring in progress for enemy type "Meteor":
|
Refactoring done for enemy type "Meteor":
|
Refactoring done for enemy type "Stupid Enemy":
|
Refactoring for enemy type "Blinky":
|
General notice: Only the "trivial" occurrences (entries in the spawn list of the level) have been updated so far. No updates as part of objects (aircrafts, projectiles) happened so far. |
Refactoring for enemy type "Blinky Tracer":
|
I think I am done for now. Refactoring can still later be continued for stuff like projectiles. |
Blocked by #19 |
Task can be continued now. |
I will start to modularize the code into single units of small JavaScript files soon. |
I should not really change much of the other code before I have put everything into its own files. |
I will playtest the refactored code soon. Should no bug become visible hindering it to be merged to master, then at least a big refactoring part can be considered done and small bugs and such can then be fixed based on code with less merge conflict potential. |
Looks good to me. I will suspend refactoring with the current intermediate result and merge this into master and roll this out on the website. |
Technical debt I need to take care of after implementing and merging issue #29 :
|
Technical debt I will soon start to clean up: |
Technical debt I need to care about later: |
Small code redundancy decrease is pushed now. |
All level bosses are now split into their own source code files. |
The usage of function variables has been quite overdone at some point. So, before continuing, the object types an own Enemy class could be created for should become the subject to refactoring.
The text was updated successfully, but these errors were encountered: