Haxe

just add a var to the class, get / set or just var, doesnt matter

I was trying to do it from the xml - guess that's where I went wrong

interesting... ... ... _should_ be possbile... but not something ive done

its not from xml, but this is how i do it... i think it should be possible to do it from xml, i feel like i added get / set support really recently... or maybe that was override / private

Ah okay, I'll try to send it tomorrow, I think I'm going to  sleep now 💤 . I had the problem in two different apps, so maybe I'll try to send the simpler app)

so yeah, you should be able to use getters / setters in xml, but the method is... well, brittle, so maybe your way is different to "the expected": https://github.com/haxeui/haxeui-core/commit/dec42fe33ef302e0a71a646c83cb8e4a7fee8e26

id still be interested in your xml approach, it should be valid, which means something in that code linked isnt right

I was just adding attributes directly to my custom component element

I was trying to get away with 
```<labelled-slider name="" min="0.0" max="1.0" pos="1.0" scale="1" precision="0" >
....
</labelled-slider>```

but just defining the names with default values just tells me that the class doesn't have fields of those names

im not sure haxeui will ever be that smart

I can use your method - I just needed to know how

you'll defo need to define things, maybe via xml in the future (though i dont see that being sensible)

no worries - this will get me what I need I think

cool - i mean, haxeui _could_ go "ah, you are defining a scale prop, cool", it could go away and create getters / setters and fill in the blanks... but then what? I mean, scale would just be a "var scale(get, set):Float"... what would it _do_ and how would express that in xml?

i think we are edging very close now to the opposite of "separation of logic and layout" 🙂

but getting there now : http://haxeui.org/builder/?d32b80ef

you are certainly giving the binding system a good tire kick, eh? 🙂