Haxe

and then haxeui-core would become haxeui?

no, i think it should stay as core to be honest

ok. well, as long as `haxelib install haxeui` doesn't work, it should be ok

then you'd start looking for what the proper name is

yeah, docs, docs, docs would help here too

the old haxeui repo also still ranks quite well on google and such..

and has more than twice the stars on github

maybe even that should be renamed to haxeui-legacy, though there's already an all-caps "IMPORTANT NOTE"

haxeui is what people first look at for "haxeui"

and it seems big notices about deprication are invisible to people

hm, there's no more maintenance / activity on the old repo at all?

then you get a note at the top like this https://github.com/vshaxe/mockatoo

but maybe people would just interpret that as "haxeui is no longer developed"

its a tough one to be honest, im not 100% sure what to do about it

renaming the repo to haxeui-legacy and archiving it would probably drive the point home 😄

then you'd need to publish haxeui-legacy on Haxelib, and get the old `haxeui` removed somehow. maybe talk to Andy about it

perhaps in the opposite order, so you don't end up with both haxeui-legacy and haxeui existing at the same time

Ian, I'll slide that next to <@126172290667773952> needing a poke to push if he hasn't already (I might have turned my GH notifications for repo off, sorry if you have and I missed it!)

Tooltips should be something given some love (contextual help is best help, IMHO), but it's not make or break by any means. Don't feel any need to rush that one on my behalf; consider it a "someone said they'd like it" sorta thing, etc.

My brain's weird lately, I'm sure this is a messy message. Sorry.

If you make a tooltip a genericized container (similar to `box`), popover menus are probably going to be much easier. Just to chuck that out there while I'm thinking about it. The context to keep/dismiss seems like the most likely headache. Pardon me while I get back to my work and not driving people crazy.

Hey, there. My haxeui app seems to get stuck while compiling the macros (`haxeui-openfl`)
looks like this line is the problem, because it works when i remove it
```haxe
    super();
    Toolkit.init();
    var ui = ComponentMacros.buildComponent('assets/ui/ui.xml');
    Screen.instance.addComponent(ui);
// THIS LINE v
    var paths = ui.findComponent('paths', VBox);
// THIS LINE ^
```

im on windows, using `haxeui-core` and `haxeui-openfl` from git. I also tried the 'new-component-method' branch