# haxe-ui
- b
bright-gpu-74537
07/23/2021, 9:56 PMesp. when it comes to native backends - u
user
07/23/2021, 9:56 PMyeah.. the inheritance chain is so big - u
user
07/23/2021, 9:56 PMAlso behaviors everywhere doesn't make it easy at first :P - b
bright-gpu-74537
07/23/2021, 9:57 PMthe inheritance chain is junk tbh... it was my attempt to split things up to be "simpler" and really, it didnt help at all - b
bright-gpu-74537
07/23/2021, 9:57 PMthe behaviours are important however - u
user
07/23/2021, 9:57 PMMany attempts at making things simpler make it more complex :P - u
user
07/23/2021, 9:58 PMYeah behaviors are fine I guess, just doesn't make it easy to follow at the beginning - b
bright-gpu-74537
07/23/2021, 9:58 PMtotally... i keep meaning to go back to "how it was" really which was just "Component -> ComponentImpl -> ComponentBase" - b
bright-gpu-74537
07/23/2021, 9:59 PMall that nonsense i added in the middle was an attempt to simplify it, and in reality it a) didnt do that and b) arguably added more complexity for no reason - b
bright-gpu-74537
07/23/2021, 9:59 PMi just hated that "Component.hx" was this huge file - b
bright-gpu-74537
07/23/2021, 10:00 PMbut i actually think if i went back to "the original way" and cleaned it up a little it would be quite alot smaller - u
user
07/23/2021, 10:00 PMMy next attempts: - fix the styles of some components disappearing somehow; not sure how easy this would reproduce without coconut, probably not that much x) - load my (image) resources at compile time; not sure how to hook into your system without using the xml files - u
user
07/23/2021, 10:01 PMAnd then I'll be able to implement more UI and find some more edge cases 😆 - b
bright-gpu-74537
07/23/2021, 10:01 PMhow are you thinking to load images at compile time? Not sure i follow - u
user
07/23/2021, 10:02 PMEither embed (base64? those images are small icons) or relative paths (a simple macro should do since
works)file:// - b
bright-gpu-74537
07/23/2021, 10:02 PMi might be misunderstanding, but you can do that now - b
bright-gpu-74537
07/23/2021, 10:03 PMhow are you loading images at the moment? - u
user
07/23/2021, 10:03 PMYeah I just need to do it I guess - u
user
07/23/2021, 10:03 PMI used
with absolute path as a temp solution (forfile://
attribute)resource - b
bright-gpu-74537
07/23/2021, 10:03 PMbut these are images that are part of your project? - u
user
07/23/2021, 10:03 PMYeah - b
bright-gpu-74537
07/23/2021, 10:04 PMso just add a module.xml, ref the directory(s) and they will be compiled into the source - b
bright-gpu-74537
07/23/2021, 10:04 PMthen you can "just use them" - u
user
07/23/2021, 10:04 PMOK uh what's module.xml? 😆 - b
bright-gpu-74537
07/23/2021, 10:04 PM - u
user
07/23/2021, 10:05 PMThanks, was looking for my haxeui tabs :P - b
bright-gpu-74537
07/23/2021, 10:06 PMi guess you are main interested in the "resources" section - b
bright-gpu-74537
07/23/2021, 10:07 PMbut, right now, in your app, if you did
it would work (on all backends)<image resource="haxeui-core/styles/default/haxeui.png" /> - b
bright-gpu-74537
07/23/2021, 10:08 PMand thats because the haxeui-core module has that image as a haxe resource that will be converted into your backend (via AssetsImpl) and shown... but haxeui-core isnt doing anything special here, you can certainly do the same - b
bright-gpu-74537
07/23/2021, 10:09 PMor more specifically, haxeui-core exposes a module that references directories that will grab any files and put them into the final app as --resource 's