https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    tables are implemented @User - let me find some examples
  • b
    oh, i thought there would be one here: https://github.com/haxeui/component-examples
  • b
    but there isnt
  • b
  • b
    thats some markup to create a table... not sure if you are using markup or not, if not it should be trivial to convert that to code
  • t
    Thanks
  • t
    Hi! 🙂
  • t
    Is there an explanation of how XML maps to "actual" classes?
  • b
    in what sense? As in how "" maps to a haxeui component class?
  • b
    or as in custom components?
  • b
    though, i guess its kinda the same now i think about it 🙂
  • b
    so... you can have a "module.xml"
  • b
    in that you can expose packages and classes for a macro to go through and build up a component registry
  • b
    these might explain:
  • b
  • b
    lemme know if thats not what you meant
  • b
    if ive understood correct, this is probably the section you are looking for: https://github.com/haxeui/haxeui-guides/blob/master/modules.md#components
  • t
    My question was more about how attributes are mapped to an object, and children too
  • b
    right, gotcha, so its basically a macro that builds code for you, doesnt really do anything else special, so if you had:
  • b
    Copy code
    xml
<vbox width="100%">
    <button text="Button" />
</vbox>
  • b
    the macro would essentially go away and create something, along the lines of:
  • b
    Copy code
    haxe
c0 = new haxe.ui.containers.VBox();
c0.percentWidth = 100;

c1 = new haxe.ui.components.Button();
c1.text = "Button";

c0.addComponent(c1);
  • b
    so nothing particularly fancy happening really
  • t
    How does it know it has to map width to percentWidth? I mean I can guess the rule there but is it specified somewhere? 🙂
  • b
    so yeah, as you would guess:
  • b
  • b
    so the UI gets parsed into objects first, then those get used to "write" the code
  • b
    main reason for the objects (apart from having this kinda pre processing) is because technically you can use JSON, YAML, X for UI's
  • b
    YAML and JSON parsers were there originally, but i dumped them as they were drifting out of sync with the main xml one
  • b
    adding them back in now would probably be fine, as i rarely make any changes to those parsers... but, honestly, im not sure how much value it would really add
1...160161162...1687Latest