https://linen.dev logo
Powered by
# haxe-ui
  • b
    I make a couple of components and add them as children to an openfl stage
  • b
    All with code
  • b
    Tried xml first, took me way too much time
  • b
    Those components aren't that complex
  • b
    sure sure, to each their own, but personally, i think xml makes maintaince a breeze, which means you can "play" with your UIs much quicker, plus if you use the @:build macro you get lots of stuff for free (like correctly typed member variables for named components)
  • b
    But they do contain a BUNCH of listeners
  • b
    that can also be cleaned up with @:bind (when using @:build macro)
  • b
    rather than "findComponent(..., Button).onClick = ..." you can have:
    Copy code
    haxe
@:bind(someButton, MouseEvent.CLICK)
function onSomeButton(_) {}
  • b
    Yeah but then I have to remember the names instead just doing`X.onChange = e -> {}`
  • b
    well, you have to remember "X" there too, no?
  • b
    I don't need to do a find, I just use casts when needed
  • b
    Mostly not cause those things are made public
  • b
    i dont really follow, but sure... as i said, its personal preference
  • b
    For my color display, I have a color Table var that has its steppers & values public
  • b
    So I can do 
    colorTab.redStepper.value = 100
  • b
    orgNameField is "" in the xml
  • b
    which is now a 
    public var orgNameField:TextField
    in the class
  • b
    So it's just autocomplete that's missing
  • b
    Probably the biggest part tho
  • b
    in the xml?
  • b
    Yes
  • b
    yeah, i guess thats a valid issue, i know the components / props so tend to not need it
  • b
    Can't that be done with a scheme tho?
  • b
    If so I might just do it myself
  • b
    yeah, i think so... i think you could auto gen a DTD schema
  • b
    + I have a website to store the scheme on
  • b
    it would probably need to happen at compile time, and put it in a temp location, since it should take custom components into account
  • b
    ie, just a static schema wouldnt work, well, i mean, it would, but it would a) have to be updated and b) not work for custom components
  • b
    so really, while its building up components haxeui could emit a schema with all properties, and then somehow link that to the xml file
  • b
    Just look at flixel's project.xml
1...103410351036...1687Latest