# haxe-ui
- l
little-oxygen-79174
03/05/2023, 1:17 AMI generally stick to the RuntimeComponentBuilder since I want to be able to modify the XML at runtime - b
bright-gpu-74537
03/05/2023, 1:28 AMit does yeah, it turns into haxe code, hence the removal of hscript as a dep.... runtime is different so it seems like its probably an actual oversight / bug - b
bright-gpu-74537
03/05/2023, 1:29 AMdo you have a repro of an issue? Or is this just a q? - l
little-oxygen-79174
03/05/2023, 1:29 AMI vaguely recall you saying something about the hscript needing a rework or being deprecated for something - b
bright-gpu-74537
03/05/2023, 1:30 AMyeah, hscript is gone... you defo do need it at runtime though... i think, it depends... if you are talking about injecting layouts with logic, then you need hscript - l
little-oxygen-79174
03/05/2023, 1:31 AMI'm sorta used to building layouts from XMLs and adding listeners to them in code at this point - b
bright-gpu-74537
03/05/2023, 1:32 AMtbf, you have given RuntimeComponentBuilder a tire kick... and thats a good thing 🙂 - l
little-oxygen-79174
03/05/2023, 1:32 AMi.e. calling
and settingcomponent.findComponent(id)
for exampleonChange - b
bright-gpu-74537
03/05/2023, 1:32 AMpersonally, i never use it... compile time is all im after - b
bright-gpu-74537
03/05/2023, 1:33 AMits your only option at runtime.. its all the macros build(ish)... they just do it for you - l
little-oxygen-79174
03/05/2023, 1:33 AMI am contemplating migrating to loading layouts with macros to see if I get any improvements from it - b
bright-gpu-74537
03/05/2023, 1:33 AMdo you want layouts to be loaded later at runtime for users? (ie, modders) - l
little-oxygen-79174
03/05/2023, 1:34 AMyeah - l
little-oxygen-79174
03/05/2023, 1:34 AMbut custom ui behaviors would need to be added by hscript - b
bright-gpu-74537
03/05/2023, 1:35 AMthen compile time doesnt make sense for you... its "set in stone"... it takes an xml file and turns it into haxe code... it cant be changed (effectively) - l
little-oxygen-79174
03/05/2023, 1:35 AMSince I have HScript users can always call Haxe code to modify components, but I think it's easier to just leave it as it is right now. - l
little-oxygen-79174
03/05/2023, 1:36 AMAnyway, a recent bug I'm experiencing; Fetching a
component and adding an<menu-checkbox>
listener only seems to call the listener when clicking on the text and not the checkbox.onChange - b
bright-gpu-74537
03/05/2023, 1:36 AM> but I think it's easier to just leave it as it is right now. i agree, if there is something that works in ComponentBuilder that doesnt work in RuntimeComponentBuilder its a bug.. for sure - b
bright-gpu-74537
03/05/2023, 1:37 AMyeah, i saw this... just havent had a chance to look, but im sure (100%) its this type of disparity between compile time and runtime component creation (from xml - its all the same in code)... - l
little-oxygen-79174
03/05/2023, 1:38 AMI feel like it has something to do with a click listener being applied to the outer menu item and not the inner checkbox, somehow? - b
bright-gpu-74537
03/05/2023, 1:39 AMno idea... i havent looked could be a bug with the component itself... no idea... will look tomorrow... ... ... ... hopefully - b
bright-gpu-74537
03/05/2023, 1:40 AMdo you have a repro? Like in the builder? That would defo make it easier for me (and also end the question of runtime / compile time) - l
little-oxygen-79174
03/05/2023, 1:43 AMI'll try in the builder - b
bright-gpu-74537
03/05/2023, 1:44 AM... .... doesnt have to be (not all things are reproducible there) - c
clever-yak-82528
03/05/2023, 6:27 AMgoddamn i have just done the jankiest thing - c
clever-yak-82528
03/05/2023, 6:27 AMhaxe can compile to javascript - c
clever-yak-82528
03/05/2023, 6:27 AMhaxe has a webassembly interface - c
clever-yak-82528
03/05/2023, 6:27 AMrust can compile to webassembly - c
clever-yak-82528
03/05/2023, 6:27 AMcombine these two together and i think i can make my haxeui stuff run in the browser - e
elegant-twilight-61392
03/05/2023, 6:28 AMhaxe can indirectly compile to webassembly too