Set of simple UI components

[Beeblerox]

• radiobutton
• checkbox
• input

For some help see this series of tutorials: http://active.tutsplus.com/series/flashpunk-ui-components/

[Beeblerox]

https://bitbucket.org/Lythom/haxepunk-gui/overview could be a good resource

[misterpah]

didn't try it, but i found this library. he extend flxtext to include a wrap function

https://github.com/fefranca/FlxUtils/blob/b9916f0c6ac353cc9cab74ee0b8f237e5889f3ff/com/fefranca/flixel/FlxTextExt.as

[gamedevsam]

The Feathers UI system is likely to become the main UI solution for mobile games build using Actionscript (considering it's backed by Adobe and Starling). I haven't looked too much into the API and how they interface and depend on Starling, but if it's possible to create a port (hopefully with little effort / changes), it might give Haxe (and HaxeFlixel) a powerful UI solution for mobile games.

http://feathersui.com/

[Beeblerox]

@crazysam I think Feathers UI is too heavy and overcomplicated for me. I will implement (port or convert) something more simple like https://bitbucket.org/Lythom/haxepunk-gui/overview

[impaler]

@crazysam Yes I see a huge need in nme / haxe for some easy to use ui. I have started my port again of as3 https://github.com/impaler/As3-Bloom to nme with https://github.com/impaler/Omni-Components I only have sliders and buttons working for desktop atm, I hope over the next two months or so I will be closer to where Sindney and I left as3 bloom's features.

@Beeblerox Yes feathers is a bit heavy the "skinable" ui I am doing is based heavily on the standard display list and events. Do you think flixel based components would have any specific advantage over nme display list?

Do you think we would have troubles overlaying nme sprites over the flixel camera? I am unable to reproduce again but I remember flickering at times with the Flixel debugger which is based on nme sprites. I should have made note of when it happened, I think it was flash target.

[Beeblerox]

@impaler flixel based components would have many restrictions, especially for cpp target. S overlaying display list based components over flixel game is better solution in my opinion. I think it shouldn't be a problem to integrate your components in flixel (maybe we need to swap flixel's mouse pointer with added components for desktops, but this isn't problem at all). P.S. I like the look of your components )

[impaler]

Sounds good, there is much work to do on my components. the scroll containers will be a challenge.

I am hoping I can have enough features and still be "medium weight" code. Somewhere in-between feathersui and minimal comps. An important point for them is being easy to make styles and theme everything.

[Gama11]

Pretty sure flixel-ui by @larsiusprime actually has radiobuttons and checkboxes, not sure about input - I guess by that you mean text input? I think it would make sense to merge those components into the core actually.

[impaler]

this issue can continue in flixel-ui repository

[anthonyzz]

I am also curious for some C# UI components recently, I can't understand the UI control tutorials well. I finally find myself prefer this JS thing.