https://linen.dev logo
Powered by
# haxe-ui
  • b
    cant seem to repro, substate doesnt have any haxeui components, just a FlxButton
  • o
    general question. i see the default heaps project sets 
    -D resourcesPath=assets
    (heaps thing) but all the paths to 
    xml
    include 
    assets/
    . is there something like that for **haxe-ui **(to declare the root asset path)
  • f
    You can have a module.xml and add resources inside
  • f
    you can take exampleherehttps://github.com/haxeui/haxeui-core/blob/master/haxe/ui/module.xml
  • f
  • o
    thanks! didn't realize there where any guides since the few I checked where blank
  • o
    does the component build macro respect the 
    prefix
    ? I get a build error 
    UI markup file "views/main.xml" not found
    Copy code
    // the view file
@:build(haxe.ui.ComponentBuilder.build("views/main.xml"))

// module.xml
<module>
    <resources>
    <resource path="assets/views" prefix="views" />
  </resources>
</module>

// structure
<root>
  - assets/
    - views/
      + main.xml
  - src/
    + module.xml
  • o
    it does not seem to
  • b
    so things like 
    @:build(haxe.ui.ComponentBuilder.build("views/main.xml"))
    are compile time, they dont really have anything to do with the resources node in the module
  • b
    ... maybe they should though
  • b
    i just wonder / worry about potential conflicts - maybe not an issue
  • o
    i was wondering that too ... don't know enough to know how much issues that would cause
  • o
    Assuming css files are also build-time (on the fact they don't update unless I compile, defined in 
    module
    ). Is there a "debug option" for runtime reload?
  • o
    looks like its using 
    haxe.Resource
    under the hood, and don't think I can do that ... I'll need to be creative
  • b
    The moment haxeui has hot reload haxe is gonna get soooooo popular
  • b
    My main 2 problems with haxeui are not even really that haxeui related. It's just: - hot reload - xml autocomplete and/or intellisense
  • b
    What that mean
  • b
    You change a css/xml file and the app updates to show that change
  • b
    Without you compiling
  • b
    I know hashlink is trying do hot reload, but idk If it would effect haxeui, as it's using non haxe resources too
  • b
    Neat
  • p
    Hot reload would require support from HaxeUI itself, but I think it wouldn't work well with the current architecture of HaxeUI.
  • b
    isnt hot reaload going to be really tricky in general? I mean, how would that work on hxcpp for example? (in general, nothing to do with haxeui)
  • p
    On hxcpp you just pay up and use Live++ :) But I think Shahar is talking specifically about Hashlink's hot reload.
  • b
    right, i have no idea how that works tbh... is there like a hot reload example to mess with? Just to understand really
  • p
    Take a Heaps app, compile with 
    -D hot-reload
    , launch with 
    hl --hot-reload
    . You can set 
    hxd.System.onReload
    if you want a callback for when reload happens.
  • b
    interesting, and as far as you know, does heaps have to do anything "special" to allow this sort of stuff?
  • p
    It calls the check_reload function at the end of each frame, but that's it.
  • b
    doesnt seem to work for me
  • b
    Copy code
    haxe
class Main extends hxd.App {
    override function init() {
        var tf = new h2d.Text(hxd.res.DefaultFont.get(), s2d);
        tf.text = "Hello World !";
    }
    static function main() {
        new Main();
    }
}
1...111211131114...1687Latest