https://linen.dev logo
Powered by
# haxe-ui
  • b
    I wanna be able to take a variable and add 
    @:edit(0, 1, 0.1)
    and it will show me a stepper from 0 to 1 with 0.1 step.
  • b
    Or 
    @:plot(100, update)
    and it will plot last 100 values in a chart, using 
    update
    as a hook for when to sample the data.
  • b
    And ideally coding all this in half a day and not two weeks. 😄
  • b
    well, i defo think that is doable... the macro would have to do something "clever" and build that all up, and change the var / stepper etc... but i dont really see anything complex there (except the macro that links into haxeui)
  • b
    > Or @:plot(100, update) fyi - there are no graphs in haxeui-core
  • b
    there is haxeui.coconut
  • b
    im far from an expert in it though
  • b
    for one project im helping on, we build a macro based system that would build property menus for types based on a number of properties
  • b
    Copy code
    haxe
    @:preserve @:menuData({usable: "${element.interactive}", order: 80})
    public var preTIMI(default, set):TIMIValues = TIMIValues.NOT_ASSESSED;
    private inline function set_preTIMI(value:TIMIValues):TIMIValues {
  • b
    changing the value of that dropdown will change the actual value in the item... but the linking etc (and the building of the UI for the popup) is all driven from @:menuData metadata
  • b
    so i think thats pretty much what you are talking about @User - but its not something that haxeui does out the box, it a system i built around haxeui for this specific app / use case
  • b
    Yeah, I would be surprised if it was otherwise. 😄
  • b
    Mostly just wondering about how hackable/flexible the experience is gonna be.
  • b
    E.g. whether I can inject new components dynamically, or does it need to be compiled all together for it to work.
  • b
    Really don't know why I won't just use HTML, but finding good UI library that's not heavier than the rest of the project... difficult.
  • b
    naw, you can defo add things at runtime... its as dynamic as any other UI framework, you certainly dont need to define everything / anything at compile time
  • b
    Alrighty, cool. 🙂
  • b
    Thanks. Adding "try HaxeUI" to my TODO list. ETA: 12 years, 9 months and 3 days.
  • b
    heh heh
  • b
    Might need to re-prioritise.
  • b
    well, good luck when you get round to it - obviously let me know if things dont go as expected - my understanding of your requirements dont sound like a problem at all
  • b
    Maybe sometimes later this year, if I find myself bored enough. 😄
  • b
    Honestly right now I'm not even sure what value HaxeUI would have, compared to other simpler HTML UI libraries.
  • b
    I guess Haxe and more powerful components. Whether that's actually worthwhile, will have to find out.
  • b
    yeah, i mean, that'd be for you to decide, for sure - if its just debug stuff then haxeui would certainly be heavier than some simple "" solution
  • b
    But who knows... the debug UI might evolve into semi-stable advanced dev UI for all the future projects. 😄
  • b
    ¯\_(ツ)_/¯
  • b
    sooo i tried it. But it doesn't work.
  • b
    Do i need to call something?
  • b
    nope, whats in that module.xml... can you zip that test app?
1...932933934...1687Latest