HaxeFlixel / HaxeFlixel/flixel

FlxText and FlxBitmapText need a common interface

Open
#2,066 10 comments 1 reaction 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

At the moment, it is not possible to write a class with text elements where it is possible to change between FlxText and FlxBitmapText due to the lack of a common base class or interface.

Having something like an IFlxText would allow us to write classes with text elements interchangeable between the two, and could replace places in flixel where presently FlxText has been used but a bitmap text might be desired, for example on sliders.

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

Start by inspecting FlxText and FlxBitmapText and the existing slider usages mentioned in the issue. Determine the shared interface or base-class requirements, then verify that text elements can interchangeably use either implementation, including in places where FlxText is currently assumed.

Written by the indexing model from the issue text.

Assessment

Domain
game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.