Haxe

<@!385014891750096896> when add a custom component, how do you handle a new xml prop ?

how to you handle myattrib on MyComponent.hx ?

I see you use "behavior" but is there any doc about it ?

depends if you want to make your component "compatible with everything" or you are happy targeting a specific backend

it's only an integer or text value, nothing more

if you want full compatibility, then yeah, behaviours, otherwise just a property on the class

if it doesnt do anything to the UI (ie, the native element, the component component, the dom element, etc) then just a "var myattr:Int" will work

but if you want it to actually do something to the UI, ie, lets say change the text, then, as i mentioned, you have two options... a setter that does something to the underlying native widget (which would only work on haxeui-hxwidgets) or by using a `@:behaviour(DefaultBehaviour) var attr:Int`

i guess i should probably write _something_ about behaviours

I want to create a component made of 3 labels

so I need behaviors...and potentially code for any backend I want to support 😦

thats not so bad, in fact, i would say, you wouldnt need to have a native component for that... that could be a "composite component" (ie, another component made of other components) with no issue

you arent adding any new components there, just Label and they are already setup with a native counter part, so:

```haxe
class MyComponent extends VBox {
    public function new() {
        _label1  = new Label();
        addComponent(_label1);
        _label2  = new Label();
        addComponent(_label2);
    }
    public var text1(get, set):String;
    private function get_text1():String {
        return _label1.text;
    }
    private function set_text1(value:String):String {
        _labe1.text = value;
        return value;
    }
    // repeat for 100 labels
}
```

ho...it was my first idea but then I saw behaviors 😉

the behaviours are different, take for example a button.... well, for a composite backend (html5, openfl, etc), that is a "Button" component, with a "Label" component

then there is a button layout that does all the positioning etc

well, then if you use that for a native backend (like wx) well, that would turn into a panel with a label in it... which _isnt_ a button :), so haxeui lets "replace" classes, so a haxeui button then becomes a wrapper for a native widget (.widget i think in haxeui-hxwidgets)

so thats all fine, now we have a correct class (hx.Button) and a thin wrapper around it.. ... however! The next issue is properties... say you say ".text" on that button, well, if its a composite it will try to create that label and add it to a the hx.Button

at best it will do weird stuff, and worst it will totally break and segfault

so the way haxeui handles this is a behaviour