SPX API Redesign

[nighca]

Problems

• Lack of non-blocking version for animation APIs, Offer non-blocking animation APIs #327
• Lack of property-transition APIs

Design Principles

• Names should be easy to understand and close to natural language.

• Existing capabilities in Scratch should have equivalent alternatives.

• The usage style should fit with the overall coding style of Go+.

  For example:

  animate "jump", 0.5
  

  In contrast, the following forms should be avoided:

  • Chainable API, like animate("jump").duration(0.5)
  • Constructing abstract objects, like newAnimation("jump").start()

• The overall structure should be neat and intuitive.

• For complex features (like animation, collision detection, etc.), the user code should describe the needs, not the implementation, leaving room for optimization by the engine.

• Keep it short, ideally no more than 3 words.

Adjustments

• Time-consuming operations (including animate, play, etc.) default to blocking, with non-blocking versions provided.
• Transition versions should have a "trans" prefix.
• Non-blocking versions should have a "start" prefix.

Details

https://realdream.larksuite.com/wiki/QF7Pwxn0tiO0n0kvllFuwluZsWb?from=from_copylink

[nighca]

Adjustments

1. Time-consuming operations (including animate, play, etc.) default to blocking, with non-blocking versions provided.
2. Transition versions should have a "trans" prefix.
3. Non-blocking versions should have a "start" prefix.

1 & 3 confirmed with @xushiwei , 2 requires further discussion.