https://linen.dev logo
Powered by
# haxe-ui
  • h
    if I wanted to get started with xml in my flixel project do I just need to add the xml file under assets?
  • b
    work for me when i move a button, but im not testing exactly the same as you, so ill have to try that...
  • b
    and yeah, for xml, you just need something like:
  • b
    var mainView:Component = ComponentMacros.buildComponent("assets/main-view.xml");
  • h
    in my Main.hx?
  • b
    that macro basically builds haxe code from the xml as if you manually wrote it
  • b
    Scaling?
  • b
    ^^ yeah, might very well be scaling
  • b
    > in my Main.hx? whereever you want want to build the component... so if you your "main-view.xml" just had "" the macro would go away and generated code like:
  • b
    Copy code
    haxe
c0 = new Button();
c0.text = "test";
  • b
    and then assign that to your component as a return value... its slightly more involved than that, but thats the basic concept
  • b
    so really, in essence, the xml macros just write haxe code for you
  • b
  • b
    its using the universal HaxeUIApp, but the general idea applies still
  • b
    there is also this: https://github.com/haxeui/haxeui-guides/blob/master/custom-components.md but i guess it could be considered intermediate, so you might want to get something really basic working first
  • b
    right, im heading off... but if you get stuck can you put your test project (the non HaxeUIApp version) somewhere and ill pick it up in the morning
  • a
    these errors that pop up a native dialog are pretty neat
  • a
    for unhandled errors
  • b
    i think thats openfl, not haxeui 😉
  • a
    haha
  • a
    does module.xml just go in the project root? e.g.
    Copy code
    src/Main.hx
src/module.xml
  • a
    looking into the themes stuff and have set up a modle like this
    Copy code
    <?xml version="1.0" encoding="utf-8" ?>
<module>
    <resources>

    </resources>
    <themes>
        <mytheme parent="default">

        </mytheme>
    </themes>
</module>
  • a
    then call 
    Toolkit.theme = 'mytheme';
  • a
    and everything is rendered invisible
  • a
    interesting, it appears to work with html5 target just not hl
  • a
    hmm
  • a
    cleaned the build folder tobe sure it wasn't cached
  • a
    and yeah html5 is all gravy
  • a
    although I cna't get anythign to change when I add a css file and edit it
  • a
    this works, so will use that :)
    Copy code
    myComponent.styleSheet = new StyleSheet();
myComponent.styleSheet.parse("...")
1...365366367...1687Latest