For everything else I've done so far, I was able to think of the design in my head and implement the code. If it didn't work, I just had to make little changes. But for the ship movement, I felt completely lost. I actually made a text document to write out my ideas and analyze them after I wrote them out. This really helped me see flaws in my design (with the help of the debugger). I kinda felt rushed to start and finish this project, so I didn't do a lot of pre-planning. Now I regret not documenting my past ideas and not planning this out. I think it would have saved me a lot of time.
I also realize my code is very unorganized, so after I get the front-end looking OK, I'm going to fix the organization of the code. I also want to create text docs to explain what each class, function and variable are for.
Here's an updated to do list:
- Have meteors break into smaller pieces, twice
- Recreate meteors once all are destroyed
- Get the "lives" displayed on the screen
- Fix bullet - meteor detection
- If time permits, add high score system
- Create documents to explain code
No comments:
Post a Comment