dannyko / gpdk Goto Github PK

update code to support polygon-polygon interactions.

check bounding box first before looping over path segments connected to nodes inside bounding box intersection

Wall ball v.2 will use the gpdk. This will also include documentation that will serve as a tutorial guide for developers looking to get starting using the gpdk.

i'm wondering if there's any advantage or usefulness of using the D3 "force" layout for any of our effects or gamedev protoypes or physics?

explore removing underscore, library and d3.timer from global physics engine

this bug was introduced after adding Vec class and refactoring code to use Vec in force, collision, reaction, and element etc.

symptom: at higher levels drones fly off in weird directions.

Rectangle class with collision/reaction cases

e.g. use code from Udacity quiz solution showing Rect collision detection - low priority update (use Polygon for now)

adjust dimensions of game to window size; for now, use SVG transforms. later, add canvas support...

Makefile to compile example game(s) coffeescript into js

(for generating production code from .coffee files)

global physics timer will allow us to reduce the total number of collision detections being executed, improving computational efficiency.

collision detection and numerical integration are not state variables and so don't really belong inside of the element class.

maybe its time to add an physics/modules/integration.coffee class providing different numerical integration algorithms and interfaces for their parameters etc.

try using the Howler.js library, thanks to @fnsport2 for the link

rewrite spacepong using the gpdk

add test folder and put physics test aka "eye candy" example number 1

speed up collision detection to reduce the number of elements checked after each positionupdate.

e.g. using d3 geom.quadtree

images not working yet but getting closer, refactored code a bit i.e. polygon.rotate() and added polygon.set_path etc.

I just learned about garbage collection overhead due to object creation / memory churn in JS and how it affects peformance in HTML5 games in particular, even simple things like splice, pop, and literals like {} create new objects... any time the "new" keyword is used, a new object is being created. We need to "pre allocate" or reuse objects as much as possible.

Since we don't want to go too extreme on minimizing garbage collection, my plan is to start with a dynamic allocation + reuse approach, where new objects are only created if an unused one is not available in the dynamic "pool" and once an object is "done" it goes in the "pool" rather than getting "destroyed" or collected by the GC.

That way, there won't need to be any static pre-allocation, but at the same time, we should be able to avoid creating any new objects if there is one that can be easily reused.

We can use the profiler to work from the top-down on the most expensive GC related churn issues first.

see:

http://www.htmlgoodies.com/html5/client/high-performance-garbage-collector-friendly-code.html#fbid=T3Okal6Nvcu

and

https://www.scirra.com/blog/76/how-to-write-low-garbage-real-time-javascript

plus

https://github.com/martinwells/gamecore.js

as well as

http://beej.us/blog/data/object-pool/

and also

d3/d3@bef1ccb

since only the parameters change we can refactor Force into a Module instead of an Object and create a new, lighter-weight ForceParam Object to manage the different types of parameters. Each element will store instances of ForceParam in a force_param array rather than instances of Force in a force array.

need a module to handle loading of assets before running game

1. add @canvas attribute to Game class to hold new Canvas layer
2. render method for element.draw() with options for SVG or canvas
3. update draw() for all Elements to support either SVG or Canvas rendering
4. move the "element.g" variable into a method switching on SVG / Canvas for each element, keep "g" for SVG case (or, make element.g a custom JS object rather than a d3 selection)
5. Root event listeners should be able to update root graphics for both SVG and Canvas

adjust physics timestep to account for variable framerates e.g.

http://gameprogrammingpatterns.com/game-loop.html

https://hacks.mozilla.org/2013/11/the-pond-building-a-multi-platform-html5-game/?utm_source=html5weekly&utm_medium=email