https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    interesting... can you try something:
  • c
    oh, wait, i need to pull latest hxwidgets
  • c
    forgot to do that before building
  • b
    still dont feel like it will fix it, if it doesnt try this:
  • b
  • b
    If I understand correctly, Imho that's a slippery slope. Composition seems like a much future proof option than inheritance because it doesn't add constraints on one lib because of another's API choices. They stay independant and free from the other, and you can still compose them together as you want
  • b
    though i agree in general, whats nice about using in inheritance is that you can use Components as ceramic visuals, ie, just "add" them
  • b
    same goes with openfl... its eventually extends Sprite, so you can just use it like it was a sprite (same for flixel, heaps, etc)
  • b
    its not a huge deal, but it does make the UI feel a little "external" to the rest of the framework
  • b
    My suggestion regarding Ceramic + HaxeUI would be to plug haxe ui via a Ceramic Component
  • b
    like this:
    Copy code
    haxe
var visual = new Visual();
var ui = new CeramicHaxeUI(); // <-- entry point of haxe ui
visual.component('ui', ui);
add(visual);
  • b
    (of course I guess you'd need more parameters to CeramicHaxeUI, but I don't know haxeui well so you know better than me)
  • b
    (docs about the Ceramic Component API: https://ceramic-engine.com/guides/components/)
  • b
    if that makes the most sense to ceramic then sounds important, out of curiosity, what are the benefits using it as a plugin as opposed to, say, just a haxelib?
  • b
    Plugins have the possibility to change/extend the config of the ceramic app, like adding a haxelib dependency, providing additional assets...
  • b
    (so haxe-ui lib could be automatically included if you enable haxeui plugin anyway)
  • b
    But if there is no need to change ceramic project config, just using haxe-ui should be enough
  • b
    gotcha... sounds like something for !billy to investigate 🙂
  • c
    commenting out the line fixed it
  • b
    im trying to stay as "hands off" with all these backends... primarily because i dont really have time, and secondarily because its interesting to see progress without intervention... (and secretly thirdly, im hoping people are keeping notes so we can brainstorm a backend guide... ... ... shhhh... 🤫 )
  • b
    cool - ill add a fix - thanks
  • c
    👍
  • b
    alright, fixed in latest haxeui-hxwidgets
  • c
    noice
  • a
    i think there's more but i'm not sure how to check all the conflicts
  • a
    i only get one at a time :/
  • a
    I remember destroy being another one
  • b
    inherit from Visual and watch it explode!
  • b
    oh
  • a
    typedef ComponentSurface = Mesh;
    just gives me 
    id
    conflict
1...145214531454...1687Latest