https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    anyways, it seems like the "preferred way to go" for the final thing is using a ceramic plugin
  • a
    huh, never considered that
  • b
    And you didn't enable arcade physics, which add even more fields to the visual type 😆
  • a
    maybe for ceramic this isn't possible 😆
  • b
    As far as I'm concerned, I would strongly discourage trying to make haxe ui types inherit from visual
  • b
    ☝️ you heard it from the boss... 🙂 No need to piss about with conflicts either - which is nice
  • a
    yeah, i think that would be wasted effort, i'm okay with mapping the obvious things through getters
  • a
    i'd like help on clipping tho 😆
  • b
    Another upside of not inheriting from visual
  • b
    is that for some haxe ui type
  • b
    you could use a Quad instead of a Mesh
  • b
    (or another visual type...)
  • b
    It's more flexible
  • b
    But anyway I'm biased, I'm really against overuse of inheritance in general. Seen projects turn really bad because of that
  • b
    yeah, thats fair enough... if ceramic users are going to be used to using a plugin type system then i would say its appropriate way to go
  • a
    I think the idea from Ian's perspective is more that It can be used as any other core "framework" type with no friction
  • a
    so you can apply your shader directly to a mesh in the normal ceramic way
  • a
    rather than doing 
    haxeui.component.surface.foo
  • a
    a small qol improvement way of working with haxeui
  • b
    keep in mind that i dont really have a perspective on this... im in favour of how ceramic users would feel comfortable using "system x"
  • b
    Yes, but at the cost of creating a lot more problems. That's why I'm suggesting the option to plug haxe-ui via a ceramic component
  • a
    yeah, it's no biggy
  • b
    There are not that many Ceramic users for now 😆
  • a
    i'm personally happy with the way things are
  • b
    > Yes, but at the cost of creating a lot more problems this is valid though, the "conflict issue" simply evaporates
  • a
    haxeui + ceramic is what i want and I get that
  • a

    https://community.haxeui.org/uploads/default/original/1X/a0977d70605c4688fcfe848563cf5551bf815893.gif▾

  • a

    https://cdn.discordapp.com/attachments/769686284318146561/1040037157538115655/unknown.png▾

  • a
    @billowy-waiter-28954 in regards to your previous question
  • a
    on how customisable are the components
1...145314541455...1687Latest