Haxe

but if you want the custom component above to take the size of the html you put in it, it'll be a little more complex as you'll need a custom layout to let haxeui know what the size of the contents of that html is

That part is fine. I have `hbox` and inside it I have `box` with a button. And I add my element to the `hbox`.

I want it to start after the button, but if I use `width:"auto"` on the box, my element gets added on top.

It works if I use percentage or some constant value.

if im understanding correctly, you might want to use a vbox instead of a box?

```xml
<hbox id="root" style="border: 1px solid grey;padding:5px;" width="100%" height="100%">
    <box style="background-color: gray;" width="auto" height="auto">
        <button text="Hello HaxeUI" />
    </box>
    <button text="Hello HaxeUI" />
</hbox>
```
Except instead of the second button, I add my own element. This works in the playground, although I would expect the box to stretch down to fill all of the space.

if you want the box to take up all the space vertically it'd need a height=100%

Right, that's more like it. Lemme play for a sec.

Yay, that seems to work. I was setting % width to the first box too, that broke it, obviously.

I'm not sure why it is, but whenever I have to do anything related to it, I get angry.

I have now finished the basic basis for the preview.
Next step: I need to find out which macros are relevant for what. (for me are relevant: adding or removing methods).

i'll be honest. this is such a hate topic right now because haxeui really has a lot of macros.

why do you need to know (or care) what the haxeui macros are doing?

Since the base of haxe ui is precompiled, haxe ui externs are used for the display.
 - base.js (contains all haxe.ui stuff @:exposed)
 - externs(*.hx) contains base.js externs without macros
For generating externs I use haxeparse. The problem here is that haxeparse doesn't know what the macros do.
Currently I am thinking about using Context.onAfterGenerate and macros directly.

my head is about to burn. Since I always here and there a few peculiarities do not consider.

For externs couldn't you just use `--macro exclude("haxe.ui")`?
I believe that should turn all classes in the haxe.ui package into externs, without you having to write a generator for that.

https://api.haxe.org/haxe/macro/Compiler.html#exclude

it just exclude them from compiler and not builds any externs

Well it turns them into `extern` classes. That seems to be what you want?