https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    main-view isnt a core haxeui component, its a custom component / view that haxeui "found" (but 100% should be included in the completion - along with any custom properties - this all works btw, its just manual)
  • b
    i was thinking about a 
    haxeui build-schema
    but i dont know if that helps or not
  • b
    --macro haxeui-build-schema
    - but again, i dont know if this helps or not
  • b
    you still need to manually add, at least, the .xsd to you xml file...
  • b
    (i just dont know a good solution here)
  • b
    ... ... ... ... ... one thing i was thinking is of scanning the asset / class path for xml files and seeing if they contain anything that isnt in the class mapping and automatically adding it then, but this seems like a HUGE can of worms
  • b
    also, technically, haxeui markup doesnt just have to be xml, it could be json, yaml (some custom format) would work fine too
  • b
    ... ... so how does that work??
  • w
    oh sorry I was chugging away at my ui
  • w
    I'm almost done, this would normally take like a week
  • e
    humans use computers slowly to make things that help them use computers faster
  • w
    thats not trolling it's just a correct statement
  • e
    no actually
  • e
    lots of humans make things that make us slower
  • w
    is there a way to put a checkbox label on the left?
  • w
    I am surprised there's no giant list of tags each for component
  • b
    you cant do that.. its not a finite list
  • e
    how is it not?
  • e
    obviously you could have custom ones, but the ones that actually do something in haxe-ui itself cant be unlimited
  • w
    dare I say, a finite subset might even be preferred
  • b
    you could create a custom component with an image at the top, and image at the bottom and some text inbetween and call it "image-sandwich"
  • e
    ok but there has to be a list of "base" components
  • b
    for sure
  • b
    but you have to remember that haxeui-core is itself a module of... itself
  • w
    head explodes*
  • b
    there is no "base", well, the macros i guess, but all the components in haxeui-core are, technically, just "included" custom components
  • w
    even just the commonly asked about ones
  • w
    or the foundational ones
  • e
    alright, so is there no way to create a list of the components included in haxeui-core itself
  • b
    from haxeui-core module.xml:
1...127512761277...1687Latest