Closed bigtimebuddy closed 3 years ago
I could live with @pixi/emitter
, or @pixi/particle-emitter
if you wanted to be explicit. That said, @pixi/particles
probably causes its own confusion by only containing ParticleContainer with no way of actually generating particles.
Good idea. I think this might be my preference:
Before | After |
---|---|
@pixi/particles |
@pixi/particle-container |
pixi-particles |
@pixi/particle-emitter |
There's a relationship, but they are still two separate things.
Yeah, that's probably the clearest naming convention.
Couple of follow-up tasks related to this:
pixi-particles
to particle-emitter
pixi-particles
to particle-emitter
@pixi
scope:clap:
This has been bothering me for awhile, there's some confusion between this library and the ParticleContainer package (
@pixi/particles
). I think we should disambiguate these two things more clearly by renaming one or both of these. "particles" is a little overloaded here.Anyone have any ideas? I'm probably more inclined to change pixi-particles to something else as opposed to change ParticleContainer. Maybe
@pixi/emitter
or@pixi/particle-simulation
?