https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    for other backends that can target js, like flixel, it would be possible to float an iframe over the top of your app and "fake" a component, but it'll look shitty, have bad integration mostly... and for native windows its gonna be really tough
  • f
    I'll look through the targets and think about it to see what I end up with... Or, I "could" just embed a flixel project inside electron to get the UI.. the question then would be how do I get them to "talk" to each other 🤔 
    document.addEventListener()
    🤔
  • b
    > inside electron to get the UI what UI do you mean?
  • b
    haxeui can already target electron (and recently tauri), via its haxeui-html5 backend...
  • b
    i presume you can also embed a flixel / openfl application in flixel? In which case you could use haxeui-flixel and embed it in electron also (ive never dont that, but i would assume its possible)
  • a
    you should just use something else in haxe if you want to go this route i think
  • a
    haxe react/reactnative works well in that regard
  • a
    but haxeui and web ui are different in philosophies
  • f
    I didn't know that haxeui could build to electron. Thanks for pointing it out I just wanted to bounce some ideas off of you guys and you were very helpful I appreciate it 🙂
  • a
    what framework are you using?
  • f
    haxeui & flixel for my project right now
  • f
    Had some free time so decided to go exploring
  • b
    and you want it to run in a native window?
  • f
    and thats how this convo got sparked.
  • f
    yeah,
  • a
    so lime (the redering api flixel runs on) can target electron, so you can select it from the list
  • b
    so cant you just build your project using hxcpp? That will result on a native window (or hashlink)
  • a
    @famous-alarm-22563 #1042896710516613170 I also figured out the config for a pretty comfy lime electron debug workflow
  • f
    that is perfect
  • f
    thanks
  • a
    or, yeah, use hashlink which is "actual" native
  • f
    I think I'm gonna go dig through some haxeui code ot see how things work.
  • p
    > and for native windows its gonna be really tough I don't think it'd be that complicated, except for the part where you have to dig deep into Flixel/OpenFL/Lime's internals. I've only looked at the macOS webview docs though, I have no idea what I'd use on Linux, or for Windows how the WebView2 stuff works
  • a
    i think the emulated css on native is so much better than actual, embedded webview css 😅
  • b
    dunno, i think creating a native component inside any of the rendering engines isnt going to be a simple task
  • a
    mostly cause, less electron dependency
  • b
    even creation of webview2 inside a, say, openfl app i doubt is simple, let alone managing that - and i still think you would end up with the "floating" thing
  • a
    and it also wouldn't be native
  • b
    sure, i mean a native component window (i dont mean a top level frame window, i mean a control window)
  • p
    On macOS, I think it'd be as "simple" as making the WKWebView render to a metal/opengl layer, turn that into a texture, and render it. It only becomes complex because eg OpenFL's architecture doesn't lend itself well to that kind of low-level things.
1...130713081309...1687Latest