Haxe

```xml
<vbox style="padding: 5px;">
    <style>
        .button {
            background-color: red;
        }

        #button1 {
            color: white;
        }
    </style>    
    <button id="button1" text="Button 1" />
    <button text="Button 2" />
</vbox>
```

Thinking to do this
https://gist.github.com/nanjizal/070aea2cc797c12097fb5c4fb7bc85a0

```haxe
var mainView:Component = ComponentMacros.buildComponent("myxml.xml");
mainView.findComponent("button1").onClick = function(e) {
    trace("do something");
}
```

and it will build the components in code as if you handcoded it with your "addComponent" "addComponent", "addComponent", etc

yer i saw that but have lot of abstracts so more macros may increase compile times

fair enough, its all in a class anyway, and looks to be pretty simple

still looks like a major PITA to maintain... but meh

I would create a method for each color but not worth the extra effort at moment

as other stuff to look at but would be nice to get an onChange...?

would I just call    onChange( new UIEvent() )  or something?

you mean you want to dispatch an onchange event?

yep dispatch when color has changed so I can grab the colors

`this.dispatch(new UIEvent(UIEvent.CHANGE))`

is there a matrix control or is that just a grid with textfield in each.

i guess table could work also, but seems overkill

I have matrix 3x3 that controls texture uniform it allows you to skew, scale, texture  and matrix4x4 for projection uniform.  So wondering the best way to allow prototype access

I don't think a single text box is really nice