mozilla / mortar-game-stub Goto Github PK

We solved the pause issue in #1, but if your phone lags (which I haven't witnessed but is entirely possible) you might still end up with a huge jump when the next animation frame comes around. I suggest we limit the maximum time delta to one second.

This is mostly meant for mobile development (for now). Let's add touch events on the canvas for moving the player around.

It doesn't make sense to "waste" space with the template title and description when running this on a small screen (e.g. in mobiles). In those cases we should make the canvas use all available screen space, and probably display the texts over the canvas itself (using white on black for obvious reasons). Should use media queries for text and positioning.

Or maybe we should even always use a full screen canvas in all the cases?

and resize accordingly

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please reach out to [email protected].

(Message COC001)

else this looks terrible in "retinas"

add one

so this is actually a "game" and we can show different stages or "screens" if need be

So when you "leave the tab" or close the app, requestAnimationFrame will stop triggering. However, due to the way we handle a steady average speed (by measureing time between each animation frame), there will be a huge jump in game play when you return to the app.

I suggest we detect leaving and coming back (blur event?? my memory is fuzzy) and reset the timestamp when we come back so we restart where we left off instead of jumping ahead.

That said, by exposing an "unpause" event (or so), we can leave it up to the developer to not start right back up when coming back but wait for keypress or something.

Basically add some more css so it doesn't look as unfinished as it does right now