HaxeFlixel / HaxeFlixel/flixel

Investigate replacing Reflection with macros where possible (FlxTween, FlxBar, FlxSlider...)

Open
#1,059 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Haxe
Stars
2.2k
Forks
522
Avg merge
34m
Merged PRs (30d)
1

Description

This would be a lot faster than the current VarTweens that use Reflection and more convenient than NumTweens with callbacks (probably also faster since callback functions are not typed statically), basically the perfect solution if we can get it to work. Tweens in tinkerbell seem to do this.

Also, tweening properties does not work on js. Using a macro would potentially allow us to work around that problem and generate tweens that call the setter function.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the current FlxTween, FlxBar, and FlxSlider paths and compare them with tinkerbell's macros/TweenBuilder.hx. Check whether a macro-based approach can replace the stated Reflection/VarTween cases and address JavaScript property tweening. Done means a scoped design or implementation decision is recorded for the affected classes.

Written by the indexing model from the issue text.

Assessment

Domain
game-dev, performance
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.