mirror of
https://github.com/flame-engine/flame.git
synced 2025-11-02 11:43:19 +08:00
1a64443cca
This is part of my ongoing effort to simplify the text rendering pipeline. My ultimate goal is to: * get rid of renders * rename formatters to renderers * make the interface complies to both All details are specified here: https://github.com/flame-engine/flame/pull/2663 As a first step to break down that huge PR, this makes a small change to TextElements to make them more useful This PR will: ### rename render -> draw draw becomes the "internal", underlying impl, raw method, that just draws the element w/ any custom options ### add a new render method that takes in more options this does not need to be extended by every impl. this is for end users and accepts parameters like position and anchor to be more in line with the renderer interface This is technically a breaking change but should have no effect for users, unless you are creating your own custom `TextElement`s. In that case, to migrate: * rename your `render` method to `draw`
Flame Examples
This is a set of small examples showcasing specific features of the Flame Engine; it's a great source of learning how to use certain things. See it live here.
This app is composed of a main menu in which you can select one of the examples and play with it. Each example is a standalone game and is contained within its own file, so you can easily checkout the code and see how it works.
For a very simple, but complete game in Flame, check the example folder inside the Flame package.
Help
If you have questions about this:
- Check the source code, the examples are meant to be simple, short, and easy to read.
- Check our extensive documentation, links to which can be found on the main repo (faq, docs folder, code/api docs, tutorials, flame-awesome).
- Join Blue Fire's Discord, we have a #flame channel where you can find lots of people to help and get help from.
- Use the
flametag on StackOverflow.