kelianb / blapika-game-framework Goto Github PK

The idea is to multiply the volume of each audio instead of setting the value.

This would allow us to balance audio properly (for example, we might want a music to be lower than the rest, or a specific sound effect to be higher) without breaking it when we modify the volume. It should also make it easier to create a volume slider (since the value simply moves from 0 (muted) to 1)

This would probably replace the globalVolume feature.

The main problem is that we have to store a few more values for each particle.

This could be useful for games that doesn't require a fixed view port ratio

This issue is related to audio loading but requires more investigation

• Opacity modifier => "glowing" particles
• Particle generator tool
• Custom functions to change dx, dy, dr, do

The content of the resource-manager isn't the one of the resource-manager, it looks like the one of the core

Right now, calling it in update causes "concurrency" issues.

Possible fixes :

• use self instead of this within _onResize (self would be engine.core)
• call _onResize with the following syntax: _onResize.call(engine.core) (overrides the "this")

dt would be the virtual time interval of the update. This can be useful for animating movement (ex : x += vx*dt).

For convenience, it could be good to have dt in microseconds so we don't have to design with insanely large values when multiplying a speed by dt, for example.

AudioManager.loop(mus1);
AudioManager.toggleMute(); // Mute mus1
AudioManager.loop(mus2); // mus2 is still played

Pros:

• We don't have to call the render function ourselves

Cons:

• Adds a check in the main rendering loop

Rename gravity and wind, and change documentation for default value (use the correct jsdoc syntax [varName=defaultValue]).

This would avoid having dozens of <script> tag in every project.
Ordering needs to be taken into account.

Add the possibility to give a function to render a particle instead of an image