Haxe

doesnt seem to be something that makes sense for the component for general use

agreed. It adds to it but not component worthy

well, i mean, i think its app specific, no? I dont think i would want / need the number of components the frame contained for my uses, but it seems like that would make sense for your app

id be interested to see if these "collapsibles" could just be "collapsible frames" with different style

ya, I really liked  how my app changed when it was applied

yeah, certainly removes alot of the clutter and keeps things "focused"

If you remove 
icon="haxeui-core/styles/shared/right-arrow-square-dark.png"
from the main-view.xml. It no longer works. It seems you need a spacer icon?

yeah, i noticed that too... thats because the act of setting the icon also creates it... so without that part the icon (image) is never created, that should go away once frame responds to "icon" css

The css variable $arrow-down-square Is that available in xml? or hx

its available anywhere css is available, but it wont work for xml props (like `icon="$arrow-down-square"` wont work)

you can use icon in frame styles now:

```xml
    <style>
        #testFrame {
            icon: "haxeui-core/styles/default/haxeui_tiny.png";
        }
    </style>
    <frame id="testFrame" width="100" height="100" text="Foo">

    </frame>
```

np, its a good catch, especially for things like collapsible frames

Now I just have to change it so the expander doesnt use the icon.  So the icon can be section specific.  sigh... 🙂

well, i think it needs a "secondary icon" which i was just about to look at

however, that one _wont_ be accessible from `#myFrame { icon: ... }`, it would be something like `#myFrame .secondary-icon { resource: ... }`

... it does beg the question of how / when it gets created though... 🤔

well, i think collapseIcon is too specific

maybe you want to do "something else" in the future with two icons... dunno

dunno, ill have a think about it... maybe we want a "component box"

... i think we might have discussed this before... ill just have to see if this is getting overly complex for a frame

ya, not sure the concept rolls to other components