http://haxeui.org/builder/?nbxtxo ?

have fun doing that in code! :-p

nice 🙂

haxe
package;
// HaxeUI stuff
import haxe.ui.components.VerticalSlider;
import haxe.ui.containers.HBox;
import haxe.ui.components.Label;
import haxe.ui.util.Color;
import haxe.ui.events.UIEvent;

class RGBAcomponent extends HBox {
    public var sRed:   Float = 0.;
    public var sBlue:  Float = 0.;
    public var sGreen: Float = 0.;
    public var sAlpha: Float = 0.;
    public function new() {
        super();
        backgroundColor = 0xD3D3D3;
        addColorSlider( 0xFF0000, function( v: Float ){ sRed = v; } );
        addColorSlider( 0x00FF00, function( v: Float ){ sGreen = v; } );
        addColorSlider( 0x0000FF, function( v: Float ){ sBlue = v; } );
        addColorSlider( 0xDCDCFF, function( v: Float ){ sAlpha = v; } );
    }
    function addColorSlider( col: Color, setColor: Float->Void ){
        var slider = new VerticalSlider();
        slider.findComponent("range-value").backgroundColor = col;
        slider.findComponent("end-thumb").backgroundColor = col;
        slider.backgroundColor = 0xc0c0c0;
        slider.min = 0.0;
        slider.height = 100;
        slider.max = 1.0;
        slider.onChange = function( e ){
            setColor( slider.pos );
            dispatch(new UIEvent(UIEvent.CHANGE));
        }
        addComponent( slider );
    }
}

then

haxe
        var shapeBgcolor = new RGBAcomponent();
        vbox.addComponent( shapeBgcolor );
        shapeBgcolor.onChange = function( e ){
            setBackgroundShapeColor( shapeBgcolor.sRed, shapeBgcolor.sGreen, shapeBgcolor.sBlue, shapeBgcolor.sAlpha );
        }

It's not too verbose?

defo cleaner (to me)

this is cleaner, again, to me

but im done trying to convince people about css/xml... 😆

Sure it's nice to have both

indeed

I'm not much into css/html

well, its not html, and its not really css (as such)

markdown

right

as i said, i dont get it, but each to their own - haxeui doesnt impose one or the other on you - and plenty of people agree with you

from flash background where you layout visually or you code it

its just increadibly verbose to me, and becomes a huge pain when you have components nested, say, 3+ levels deep

but also it's because if I understand code I can translate to xml css as well

I used a lot of XAML and it was not easy to make MovieClip type things atleast it seemed not, and often was hard to get the XAML right sometimes seems easier to dynamically do it in code

I mean in the past days I would probably have a for loop for each color but not really worth it.

I remember flash had generator in the early days it was a bit like cold fusion.

sure, well, as i said, each to their own - but either work just as well, and for sure there are times when xml just wont do what you want it to do

like some type of fully dynamic ui based on something

you could use xml (kinda) but would seem worth it

But it's quite nice as I guess the slider setup could be a component defined in xml and then instanced in the rgbacomponent

would need another class but maybe clean that way

yup... and you could get even more snazzy and make the component autobuild (via macros) andget it all nicely wrapped up

yer it's definitely interesting.