https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • a
    with the caveat being, the backend needs to implement the action but not the component
  • a
    so a canvas component would need to know how to draw a line, in the backend you write how you draw a line on the backend
  • a
    but if you don't implement drawing a line, you can't use the canvas component
  • b
    Alright
  • a
    this might make it a bit more obvious
  • a
    this is all the files a backend may need to implement
  • a
    componentsurface
    may be a 
    flxsprite
  • a
    imagesurface
    may be a bridge to flxgraphic etc
  • b
    Hmm
  • b
    Hi
  • b
    Specifically the intention is to be able to use any GUI component provided by a UI framework backend, even if it does not exist in any other UI framework backend
  • b
    (of course, mixing backends is not allowed)
  • b
    For example, if we where to make a backend for Android's View System, then we should be able to use every single component from that view system, such as RecyclerView, ConstraintLayout, and others
  • b
    But im not sure how to go about that
  • o
    probably easier to use a java android game engine as the basis, so you just need an app view or something to control the user space and provide the mouse methods etc..
  • o
    for instance libgdx could be used
  • o
    probably need to look otherwise at some of the Kotin non xml android stuff
  • o
    for instance maybe could have some stuff. But haxe-ui backend would need fairly lowlevel I suspect. So need to look at how parts of the android internals fit together as much of the xml structures in android would be too high level, that's why a java game engine that runs in android would be cleaner to misuse for this?
  • b
    So thats not really how haxeui works, haxeui would abstract android native ui into haxeui, so you wouldnt use andriods layout system directly, you would use haxeuis layout system (and components) and the backend (haxeui-android) would be responsible for using the appropriate native layout
  • b
    alright, this should be working now - latest haxeui-hxwidgets, composites are fixed too (latest haxeui-core), but i dont think you currently care about that 🙂
  • i
    having trouble getting it to work still
  • i
    trying a clean build again in case of cache shenanigans
  • b
    hmmmm
  • i
  • b
    right, actually, your repro doesnt work right, so there still might be something off
  • b
    oh, thats a different issue entirely
  • b
    alright, can you try that?
  • b
    also, btw the your repro isnt using datasources correctly, 
    new DataSource
    should be 
    new ArrayDataSource
  • i
    ah forgot that one
  • b
    has nothing to do with the bug(s) though - which i think are squished now... ... ... ?
1...160416051606...1687Latest