madhavm-117 / pacmanjs Goto Github PK

• Create normal candy for pacman to eat, and populate in map
• Create super candy for pacman to eat, and populate in map
• define what happens when pacman eats the super candy
• track score on eating normal candy, for pacman

• implement a start-up and pause menu

Start-Up Menu should have options to

• Start a new game
• View High Scores
• Create a custom level
• Edit settings (if any)

Pause Menu should have options to:

• Resume Game
• Edit settings (if any)
• Quit to Start-up Menu

• Create a Ghost Sprite
• Define the Ghost Pen, in each level, which will serve as the spawn area for the Ghosts, when eaten by Pacman

Planning to use this issues as to track references that we have been looking at.

Here is a video that I used as the basis to create the initial template project:

• https://www.youtube.com/watch?v=3EMxBkqC4z0&t=485s

Here is the final source code, associated with that video:

• https://codesandbox.io/s/z2pqr9620m

Planning on setting up:

• eslint
• prettier

along with a pre-commit hook to enforce that all code is formatted uniformly, before pushing.
I'll take a look at this, when I get time.

I'll set up a framework with Mocha/Jasmine and start off a couple of tests.

Let's try to follow these practices:

• Testing out the logic of each code segment with unit tests
• TDD, sooner rather than later
• Testing the canvas drawing functions with Canteen and Rabbit that will use a reference catalog to test image drawing on canvas. (Do this only for quality improvement purposes later - Don't waste time drawing detailed pictures for catalogs)

A good intro to TDD with canvases in JS:
https://stackoverflow.com/questions/4406864/html-canvas-unit-testing

Want to be on the same page, regarding code structure and organization.

• Let's keep the top level directory, clean.
• All typescript/javascript should be in the src directory.
• organize files into an appropriate folder structure, where possible. A flat structure will get too big, and overwhelming, quite quickly.
• avoid files getting too large.
• create classes where possible.
• avoid using the any type.
• be explicit with types, where possible
• indentation to be done with tabs (I've configured IDE, to represent tabs as 2 spaces)

Creating levels by hand, will not be an easy task. ideally, we should some basic game-like UI, which will allow us to define custom levels, controlling things from placement of walls, to the color and themes.

• implement basic level creator
• should preserve the ghost pen, through all custom levels