https://linen.dev logo
Powered by
# haxe-ui
  • b
    Copy code
    haxe
        var a = new Application();
        a.onActivate = function(app) {
            app.applicationWindow.title = "User title";
            
            var button = new Button("Click Me!");
            button.margins = 10;
            button.onClicked = function(_) {
                button.label = "Thanks!";
            }
            app.applicationWindow.setChild(button);
            
            app.applicationWindow.present();
        }
        a.run();
  • b
    (my attempt to "haxify" it a little)
  • b
    Is that using wxwidgets or straight gtk
  • b
    gtk directly
  • b
    Very nice
  • u
    how did you do it?
  • b
    hxcpp externs and then some wrappers to make it "nice"
  • s
    i'm not sure how good of an idea it is to have direct gtk
  • s
    wait with how wxWidgets work it uses the builders system lol
  • b
    ?
  • n
    very nice
  • n
    this man is unstoppable
  • b
    ... man, its taken me waaaaay too long to get that "feeling" right...
  • b
    revamped the whole "action system" in the process.... thats why it took me so long, because my original action implementation was bad - so i spent a while trying to work around it rather than just redoing it again (better)
  • b
    just take time to make it perfect :P
  • b
    🙂 tbh, i dont really know why my initial impl didnt use the haxeui event system... but it didnt, it used this "additional" method of calling "actionStart/End" directly on components... which made intercepting these calls (like in the case of dropdowns where the behaviour is different) hard / impossible / hacky...
  • b
    now it uses events (like everything else, doh) and its all fine...
  • b
    so basically, i came up with a shitty impl and then tried to work around it when it was being shitty rather than use the tried and tested inbuilt methods to achieve this type of stuff... 🤦‍♂️
  • b
    You always learn something new! :) I'm currenlt search a gdi+, cocoa, x11, waylands rendering library or thinking to make a skia backend for haxeui. After working a bit with c in the last days i think i can now work on this a little bit. I would like to have something smaller. In the direction of window management and 2d software canvas c library. I'll do some more googling xD
  • b
    funny coincidence is that i saw nuklear motioned in the kha discord a few days ago - could be interesting, though i wonder how well its component set fit into haxeui's
  • b
    though im sure whatever it uses for rendering could certainly be adapted, but then i wonder what are its benefits over, say, kha directly?
  • b
    To be honest, I'm looking for advantages myself before I implement anything. In the past, people used to say: Use software renderers for surfaces. So native gdi+ applications etc. Only that I currently know that it has been called "better" I currently also know rather less.
  • b
    alternative, implement a software renderer in kha xD
  • b
    im no gfx expert by any means, but im pretty sure now its the opposite, ie, software renderers are slow and "old" and everything ideally should be done in the gfx card (where appropriate), again, im in now way an expert, but thats the feeling i get now-a-days
  • b
    ¯\_(ツ)_/¯
  • b
    i see alot of "hardware accelerated xyz", but i dont very often see "CPU restricted abc" 😄
  • b
    is it possible to run a pc without a gpu? Hmm what about integrated gpus and cpu rendering. There are so many things I wonder about but there are really few answers.
  • b
    i think fallback to CPU is the way most renderers do things... but i could be 100% wrong / misguided here
  • b
    That's just the problem xD most developers don't really know about it and somehow hardly anyone seems to care. Maybe I'll make a post on stackoverflow to clarify this whole topic, maybe there's someone there who knows all about it.
  • b
    i betcha some folks around here would have a pretty good answer... Rob springs instantly to mind
1...853854855...1687Latest