Tracking Issue: Curves Working Group Tasks

[mweatherley]

About

The Curves working group exists to implement the Curve API described in this RFC and integrate it into Bevy's existing codebase (primarily in math and animation).

The design document for this group is here.

This working group is coordinated in this Discord channel.

If you are interested in contributing to this effort, please check in on Discord first — and, of course, external reviews on related PRs are always welcome.

Tasks

• Implement the Curve API itself.
  • Implement a viable minimum usable as an interface. (Blocker for everything.) (A Curve trait for general interoperation — Part I #14630) (A Curve trait for general interoperation — Part II #14700).
  • Extend SampleCurve and UnevenSampleCurve APIs for consumers.
  • Implement Reflect on concrete curve types from the API. (Blocker for bevy_animation integration.)
  • Extend the API to include non-allocating sampling API for curves with dynamically-sized array output. (Blocker for bevy_animation integration.)
• Integrate the Curve API with bevy_animation.
  • Replace each component of VariableCurve (translation, rotation, scale, morph weights) with a type that implements the associated Curve trait. (Curve-based animation #15434)
  • Refactor AnimationTargetContext to sample from new VariableCurve components instead of doing its own interpolation.
  • Benchmark animation update performance and compare the refactored version with the existing one.
• Integrate the Curve API with bevy_math.
  • Perform design work on shared API for producing and consuming geometric curves which may be constrained by the input quality (e.g. C0 vs C1 curves).
  • Implement curve-production API for CubicCurve and implementors of CubicGenerator.
  • Implement curve-production API for RationalCurve and implementors of RationalGenerator.

Beyond

This section is for tracking related tasks outside of the scope of the present working group proposal that may be spun off into external issues when this work is completed (or advanced to a sufficient state).

• Investigate the inclusion of more common easing/tweening functions into Bevy itself.
• Improve the Reflect implementations for adaptors in the Curve API so that the adaptors are Reflect when their bases are.