An open API service indexing awesome lists of open source software.

https://github.com/erickzanardo/flame_canvas

👀
https://github.com/erickzanardo/flame_canvas

Last synced: 24 days ago
JSON representation

👀

Awesome Lists containing this project

README

        

# Flame Canvas

![coverage][coverage_badge]
[![style: very good analysis][very_good_analysis_badge]][very_good_analysis_link]
[![License: MIT][license_badge]][license_link]

Generated by the [Very Good CLI][very_good_cli_link] 🤖

(Experimental) Flame Visual Editor

Nothing concrete to see here yet, still cooking this and unsure where it will lead 👀.

# Development roadmap

- [x] Basic objects and Scene creation
- [x] Basic project data serialization/deserialization
- [ ] Basic project code generation
- [ ] Working basic pong game made with the editor
- [ ] Hitboxes
- [ ] Sprite and Sprite Animation support
- ...more to come, suggestions welcome!

# Pillars

# Flame is a code first engine

Flame is a code first engine, which means that any visual editor tools should be optional. In light of that
Flame Studio should be:

- Not be used as a code editor, it will generate code for components and scene,
but logic will be written by the user in their own editor of preference.
- Flame Studio can be easily "pluggled out" of a project simply by not being used anymore. This implies that
the code generated by Flame Studio is readable and easy to understand.
- Flame Studio uses convention over configuration in some cases, that is done specially because of the previous
bullet point. The Editor will always try to guide the user through the conventions though!

---

[coverage_badge]: coverage_badge.svg
[license_badge]: https://img.shields.io/badge/license-MIT-blue.svg
[license_link]: https://opensource.org/licenses/MIT
[very_good_analysis_badge]: https://img.shields.io/badge/style-very_good_analysis-B22C89.svg
[very_good_analysis_link]: https://pub.dev/packages/very_good_analysis
[very_good_cli_link]: https://github.com/VeryGoodOpenSource/very_good_cli