HaxeFlixel / HaxeFlixel/flixel
Abstract BitmapData to allow ram dumping
Open
Nobody has claimed this yet.
Assets
Rendering
Structure
- Dominant language
- Haxe
- Stars
- 2.2k
- Forks
- 522
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
Rough Idea
Deprecate myFlxGraphic.bitmap, any other uses of Bitmap and add some graphic.startManipulation() method which returns an object with Bitmap's drawing tools, which somehow requires a finalizing end() call to dumb the Ram
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the uses of BitmapData, Bitmap, and myFlxGraphic.bitmap across the repository, then read the relevant graphics abstractions and platform-specific code. The issue does not identify files, tests, or a settled API design; completion would require an agreed manipulation lifecycle and a defined way to dump changes to RAM.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100