https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    hard to know the best approach
  • b
    (in an efficiency sense)
  • c
    multiple graphics might be better, given the background image can change dynamically through 
    style
  • b
    yeah, you could be very right, and it sounds alot easier to implement too
  • c
    where should I look into about this issue?
  • c
    I can try fixing it
  • b
    there is likely a StyleHelper in the haxeui-heaps lib... two secs, lemme confirm that
  • b
    yeah: haxe.ui.backend.heaps.StyleHelper
  • b
    there is the slice 9 stuff there, maybe it all need to be sorted
  • c
    wow this inheritance tree of 
    Component
    ...
  • b
    yeah :/
  • b
    the idea was to simplify it as Component was getting HUGE
  • b
    previously all of that code was in Component
  • b
    so the intention was to split it out into smaller chunks
  • b
    the inheritance tree certainly wasnt needed for any reason other than an attempt at "neatness" (not sure if it worked to be honest)
  • c
    the current problem is that 
    Component
    extends 
    h2d.Graphics
    It is not immediately clear how to use multiple 
    Graphics
  • c
    I think using composition instead of inheritance could possibly make it simpler (and easier to test too)
  • b
    yeah, so maybe it could inherit from something else "heaps like" rather than graphics and then add a graphics object to it.... not sure
  • b
    my knowledge of heaps is a 1 out of 100 i would say 😄
  • c
    > I think using composition instead of inheritance could possibly make it simpler (and easier to test too) for example pretty sure 
    ComponentEvents
    could be a separate class e.g. 
    EventEmitter
    or the like
  • b
    yeah, its a valid point for sure... what happened was at some point months ago i was sick of scrolling through 1000's of lines of code in Component and thought "right" im just going to move some of this out of here!
  • b
    but in reality i moved a few 100 lines out, and arguably made the hierarchy harder to follow :/
  • b
    there is still ALOT i could move out of Component into the base classes to be fair, but i havent done so as im not convinced myself about the change
  • c
    I think heaps 2d is quite like openfl, i.e basically based on a display list/tree
  • b
    it seems fairly similar, yeah
  • c
    and 
    h2d.Object
    is the "base" container class
  • b
    right, so maybe it should be an Object with graphics objects added to it?
  • c
    maybe could use that, then "addChild" some 
    Graphics
    into it
  • c
    exactly.
  • b
    yeah
1...273274275...1687Latest