https://linen.dev logo
Powered by
# haxe-ui
  • b
    and it should be consistent, it shouldnt be a "sure if you want"
  • r
    Right now there are a billion ways to style something, if anything that should be minimized.
  • b
    that wouldnt bother me so much, as a static extension, but its still more code to maintain for very little reason
  • b
    Tbh, you're right, still think it's a nice feature to have tho
  • b
    ... ... i dont :-p
  • b
    i dont even really get why people are even using code rather than xml, it literally just writes pages and pages of code for you and 10 times easier to maintain (imho)
  • b
    hmm ... build macro that auto-generates the function ? then you just need to add the annotation to the classes that need it
  • b
    is there?
  • r
    I would say so, yeah.
  • b
    yeah, you dont even need to use the @:build function, you can just use ComponentBuilder.fromString (or something) and it will put the haxe code there, the @:build function does similar and a bunch of other things
  • r
    At least in code, not sure about XML
  • b
    maybe im not following, like how?
  • b
    hmm not a billion but x times y times z
  • r
    I am busy right now, so can't dig up examples
  • b
    I don't like not having autocomplete, and I like having my components and listeners in one place
  • b
    rightyo, i mean, it all comes down to the css engine at the end of the day, and two properties that are used "style" (which should be computedStyle) and "customStyle" (which should be style)
  • b
    why would you not have your components and listeners in one place?
  • b
    i guess the auto complete is valid, but if its a valid prop in the component, its a valid prop in the xml
  • b
    thats it
  • r
    Next time I use HaxeUI i'll have to use XML
  • r
    HaxeUI code experience isn't great
  • b
    tbh, there is nothing you can do in xml, you cant do in code...
  • b
    all of it turns into haxe code eventually
  • r
    Of course, but managing all of it gets messy
  • b
    is there no way of having autocomplete for haxeui xml? or is it just something that hasn't been addressed yet
  • r
    My code for my Wordle code was a disaster, but to be fair I was just trying to put together something fast
  • b
    for sure - but i dont think thats a haxeui problem i think thats a "complex ui in code" problem... java SWING was abysmal for this reason
  • b
    i think its possible to auto generate a DTD on the fly
  • b
    I don't really make complex stuff on code with haxeui
  • b
    and then autolink that to the xml file
1...103310341035...1687Latest