https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • a
    then you may have
  • a
    addComponent
  • a
    which core would then call so it can add a component to the scene/display tree/whateve the backend needs to do to render to screen
  • a
    but you wouldn't need to worry about the backend yourself really
  • b
    Hmm alright
  • a
    no backend has "unique components"
  • a
    components are all in 
    core
  • a
    any components that "arent implemented" just haven't had the instructions made on the backend
  • b
    Like, if a particular backend has a ui element that you want to use, but it is not available in other backends Can that ui element still be used?
  • a
    that particular issue doesn't occur
  • a
    no backend defines specific components
  • a
    backend just does things for core
  • a
    core says "draw this" backend says "okay, this is how we do it"
  • b
    Like the ui framework itself that a particular backend uses
  • a
    backend doesn't know what it is drawing
  • a
    hmm, not sure how else to say this 😄
  • a
    there is no specific ui framework to a particular backend
  • a
    all components that any backend uses are all in haxeui-core
  • a
    no backend has specific components
  • a
    so you can make a pure haxeui app in openfl, decide you want to switch to heaps and as long as you yourself have no heaps specific code
  • b
    Like, if Flixel has a specific ui element i want to use in haxeui, how can i do so?
  • a
    you can just switch with pure haxeui code
  • a
    broo are you reading my replies? 😄
  • b
    I am
  • a
    there is no flixel specific ui element
  • a
    such a thing doesn't exist
  • b
    Oh
  • a
  • a
    so you see this page right
  • a
    all of these components, and the code are available on all backends
1...160316041605...1687Latest