https://linen.dev logo
Powered by
# haxe-ui
  • s
    yh... you don't generate html so it wouldn't make sense to generate xaml
  • b
    or you could take a haxeui xml and turn it into xaml via xslt ot something... but my guess is thats going to cause more problems that it solves
  • b
    if you write a haxe app (no haxeui) with a button, listview and textfield using winui3, thats half the battle
  • s
    yh first step is writing bindings in the first place
  • b
    exactly, first you need to interface into winui3... and that looks like its going to be a pain.. the cpp is complex and the c# wont run on my machine as its... ... well, i have no idea
  • b
    once you can do that from haxe, the rest is just "honouring" what haxeui sends your way... but its not a small task... and the initial part of using haxe for winui3 is enough of an effort for me to realise i dont have time at the moment
  • s
    wxWidgets qt apparently can build on windows but then you have to use mingw
  • s
    and as i've noticed it's not in the most production ready state
  • b
    yeah, thats my opinion also... and, thats assuming it would allow you to theme things in a more custom fashion - so you might just be in the exact same place
  • s
    at least qt looks not absolutely ugly
  • b
    imo the best option for a fully themeable "native" (qt isnt native at all - it just appears that way) app is qt - ive have half written externs and a half written backend, but there was issues with random crashes which means my externs (or more likely my wrappers / haxeui) were badly written / concieved
  • s
    qt isn't native?
  • b
    not in the slightest, its all "custom drawn", its just done very well so you dont noticed - but there are tale tell signs
  • b
    a qt button isnt an OS button at all
  • s
    not even on plasma 😲
  • s
    wow
  • p
    There is no such thing as "native UI" or "OS buttons". In the end "native UI" looks native because it uses the specific toolkit used by all the DE's apps & UI. For GNOME it's GTK. For KDE it's Qt. For Windows it's some Microsoft library, and for macOS it's AppKit (in the past it used Cocoa)
  • b
    OK, well, i mean native to the libs... qt doesnt say to the OS "give me a button" it says "give me a window and a device context and ill draw it"
  • b
    wx does say "give me a button"
  • p
    > say to the OS *say to the OS's UI toolkit
  • b
    fine, splitting hairs... ... says to the OS's UI toolkit 🙂
  • b
    my point is that qt talks to the OS ['s UI toolkit 😉 ] at the most basic "give me a drawing surface" level
  • b
    it handles state changes, it handles internal lifecycle, etc, etc
  • r
    You could argue that GNOME's ui toolkit is libadwaita which is built on top of GTK lol
  • p
    (Technically that's only true on Windows, on Linux it asks the window manager/compositor) (I'll stop splitting hairs now)
  • b
    so in qt on linux it creates a gtk button? Or creates a surface and draws a button similar to how gtk does?
  • b
    (assuming the underlying OS using gtk ofc)
  • p
    QT asks wayland or x11 for a window + context and draws stuff.
  • b
    exactly, thats my point
  • r
    Qt is on the same level as GTK.
1...918919920...1687Latest