I'd like to share a concept I have for a morphing API. I don't have a functional proof of this concept implemented yet, just a short file with some stub structs: https://github.com/teodosin/bevy_gen_gaussian/blob/main/src/gaussian/mass.rs. Still wanted to share this just in case it's interesting.

The basic idea is to decouple the gaussian cloud entity from the form that it's supposed to take. This would be done by separating the cloud into two components, a Mass and a Form. The Mass component contains or references that gaussian cloud itself and is what gets rendered in the end. The Form component on the other hand can be many things. It could be a link to a .ply or .cloud gaussian asset directly, a reference to a different type of asset like a mesh, an SDF function, or a particle simulation. Changing the Form would trigger the interpolation of the current Mass to the new Form.

The infrastructure underneath would silently handle the conversion from the underlying Form asset to the specific cloud Mass, as well as the interpolation between them and the necessary padding or swapping #107 to the correct amount of gaussians. A truly flexible API would also handle the splitting and merging of Masses to or from multiple Forms, but I don't have a clear vision of what that would look like yet.