flixel | addons | ui | demos | tools | studio | templates | docs | haxeflixel.com
NOTICE: this project is in early days of development! Things are expected to change and/or break. Documentation and features are still very rough, but they will eventually mature in the near future. Check the ROADMAP to have an idea of how the project will evolve.
Flixel Studio is an embeddable, in-game editor for HaxeFlixel. Simply put, when enabled in a project, Flixel Studio will turn the existing Flixel debugger into a full-featured editor. You can then organize game elements using layers, edit tilemaps, change properties of game objects, among many more things.
The philosophy behind Flixel Studio is to empower game developers with tools that integrate directly into their game runtime/code.
- Full-featured in-game editor.
- Load and modify tilemaps.
- Edit properties of game objects, e.g. position, velocity, etc.
- Manage game elements in layers of content.
Get the latest development version from Github:
haxelib git flixel-studio https://github.com/Dovyski/flixel-studio.git
NOTE: in the future, you will be able to install flixel-studio
from the haxelib
repository.
Go to the folder where you have your project files, open the file Project.xml
, then add the following:
<haxelib name="flixel-studio"/>
Usually libs are listed in the libraries section of the Project.xml
file, which will probably look like the following after you add flixel-studio:
<!--------------------------------LIBRARIES------------------------------------->
<haxelib name="flixel"/>
<!--In case you want to use the addons package-->
<!--<haxelib name="flixel-addons" />-->
<!--In case you want to use the ui package-->
<!--<haxelib name="flixel-ui" />-->
<!--In case you want to use nape with flixel-->
<!--<haxelib name="nape" />-->
<haxelib name="flixel-studio"/>
After installing and adding flixel-studio
to your project, you are ready to start using it. To make Flixel Studio available for use in your game, call flixel.addons.studio.FlxStudio.create()
anywhere in your code, e.g. in your Document class or in your FlxState
's create()
override.
Below is an example of a call in the game's create()
override:
override public function create():Void
{
super.create();
// [your own code here]
flixel.addons.studio.FlxStudio.create();
}
Below is an example of a call in the document class:
package;
import flixel.FlxGame;
import openfl.display.Sprite;
class Main extends Sprite
{
public function new():Void
{
super();
addChild(new FlxGame(0, 0, MyInitialState));
flixel.addons.studio.FlxStudio.create();
}
}
When you compile and run your game, you can just bring up Flixel's debugger (by pressing the key below Esc), then click the interaction tool in the bar at the top.
When Flixel Studio is enabled in a project, the interaction's panel of tools on the right have more items, e.g. a tile tool. Addionally, you will see a few new debugger windows showing layers of content, etc. Enjoy your in-game editor!
The development process is a little bit rough right now. It's basically me coding and changing things a lot, documenting things very superficially along the way. At some point, the APIs will stabilize and it will be a lot easier to join the party.
If you want to help now, you can take flixel-studio for a ride and send me your feedback, or suggest a feature, report a problem, or even send a pull request. Check the ROADMAP to have an idea of how the project should evolve.
Flixel Studio is licensed under the terms of the MIT Open Source license and is available for free.
See all changes in the CHANGELOG file.