XML Issues about flixel-ui HOT 7 OPEN

to be honest, flixel-ui is a very one of the least maintained parts of flixel. I personally don't use it, and I highly recommend haxeui-flixel instead.

from flixel-ui.

Oh. I had no idea that that existed. Is it compatible with flixel in that its components can be added to states and such?

from flixel-ui.

yes, I'm working on an example for my Newgrounds API, I'll upload it tomorrow morning and share here.

from flixel-ui.

@DalekCraft2 Here's is my example:
https://github.com/Geokureli/Newgrounds/blob/flixel-ui/test/haxeui-flixel/Source/states/IntroState.hx#L17

classes that use ComponentBuilder.build will extend FlxSpriteGroup, and can be added to your state, or other groups.

from flixel-ui.

I hope this repository won't be abandoned completely! I rely on it and its useful features for my project. I'll continue to try and maintain as long as we can still get PRs through.

from flixel-ui.

I realize that porting an existing project to haxe-ui is no small feat, but to be absolutely frank, I despise flixel-ui on a fundemental level and most people who do use it tend to use it for one small thing, and I've seen many people in the haxe forum talk about dropping it entirely.

it would make much much much more sense to recreate haxe-ui's components (without the macro xml building) in a new Flixel-UI repo than to try and maintain flixel-ui IMO

from flixel-ui.

I use things like FlxUICursor and the FireTongue implementation and I don't know how long/difficult it would be recreate all of this in haxe-ui.

I'll keep an eye on the progress of haxe-ui, but deadlines prevent me from dropping this library at the moment. If there are plans to shutter this project, official references to it such as RPGInterface should be removed to prevent misguidance and confusion.

Edit: For clarity and in the meantime, I'm more than happy to continue to help with this project!

from flixel-ui.