https://linen.dev logo
Powered by
# haxe-ui
  • b
  • b
    kinda goes through all of the options iteratively
  • t
    Copy code
    haxe
var button1 = new Button();
        var button2 = new Button();

        button1.onClick = function(e) {
            button1.text = "Thanks!";
        }

        button2.onClick =  function(e) {
            button1.text = "Thanks!";
        }

        addComponent(button1);
        addComponent(button2);
    Is that right? Just ignoring XML for now
  • b
    yeah, im assuming when you click on button2 you want to set the text of button1?
  • t
    oh-
  • t
    lol
  • t
    I didn't notice this
  • h
    The xml is cool though. Well I think so having played a little with it. Makes iterating over layout changes really easy
  • b
    yeah, personally, i think xml (or some type of markup) is essential when building UIs - it just gets really hard to maintain for larger apps
  • h
    One key reason I am interested in haxeui is the markup based approach tbh. I'm only messing with something small but it is nicer to have the layout in its own file without tons of other code around it
  • t
    uh why do the size and alignment of buttons are not the same when doing in haxe code
  • b
    im not sure what that means, haxeui + xml just "writes" haxe code for you, its not doing anything radically special - so your app must be doing something strange / different to when you use xml
  • t
  • t
    ah that's the one
  • b
    right, if your MainView extends Component, then yeah, it wont layout any of its children since its just your bulk standard component with a DefaultLayout (which does resizing, but not repositioning)
  • t
    im just trying to do the html5 version of this with haxe and no XML
  • t
    for testing purposes
  • b
    Copy code
    haxe
class MainView extends VBox {
    public function new() {
        super();
        addComponent(new Button()).text = "Button 1";
        addComponent(new Button()).text = "Button 2";
        addComponent(new Button()).text = "Button 3";
    }
}
  • b
    thats obviously not the "full app", but that would be the right layout etc...
  • e
    chaining
  • e
    do you have a 
    setText
    method or something so you could do like 
    addComponent(...).setText('button').otherthing(...)
    ?
  • b
    i was toying around with a "haxeui dsl" at one point, so you could do something like:
    Copy code
    haxe
beginBox()
    .beginHBox()
        .button().text("button 1")
        .button().text("button 2")
        .button().text("button 3")
    .endHBox()
.endBox();
    but decided it was entirely useless (and work to maintain) since you can just use xml
  • t
    after reading that section, I comprehend that 
    @:build
    is better than 
    ComponentMacros.buildComponent
  • t
    I'm not sure, why would you se the second, isn't it the same but you have to use .findComponent, @:build just removes that redundancy
  • b
    i would say so, yeah
  • b
    i guess its mostly there for legacy type reasons, and also, maybe you might be too lazy to setup a class, etc... quick and dirty basically
  • t
    mhm yeah.
  • t
    how would you modify the position of a 
    Component
  • h
    I'm trying to boost the size of a text attr. I checked the Frame doc and it looks like frame doesn't support font-size. If I set the style generally that works but affects all text everywhere. I haven't be able to come up with a selector that will target the text attr of a frame. Is there a way to do this ?
  • h
    Is there doc somewhere about the CSS supported ? What version or what specific features ? I'm trying 
    frame > label
    and it seems like it's doing 
    frame label
    . I could be wrong but it looks like that. I got it working with 
    #id > label
    as a selector but 
    element > element
    doesn't seem to work. Should it ?
1...112911301131...1687Latest