https://linen.dev logo
Powered by
# haxe-ui
  • b
    It has a schema
  • b
    And it works great
  • b
    but their defintion is static
  • b
    Haxeui xml is also static
  • b
    Or not...
  • b
    no, its not
    Copy code
    xml
<vbox>
    <my-custom-component someProp="22" />
</vbox>
    is perfectly valid, and would lead to a component class MyCustomComponent with a "someProp:Int"
  • b
    So you could have autocomplete for static types
  • b
    Still solves 95% of the problem
  • b
    well, i think if you are gonna do it, it makes sense to do it properly, plus, its less to maintain
  • b
    and for me personally, i use custom components ALL the time
  • b
    also, if it didnt have all the properties (ie, just the static ones) then i think vscode will say "" is invalid (ie, red squiggly lines)
  • b
    this keeps this super nice and organised and contained...
  • b
    imho, even with your ezworksheet, even your panels (regardless of complexity) would be custom components
    Copy code
    haxe
@:build(...)
class LineSettingsPanel extends VBox { }
    But thats if i was making it ofc :), and its defo a personal pref
  • b
    i need to say that i actually love this code/xml duality
  • m
    Hi, been following this chat for the last couple of days, and I have to say that I also love haxeUI code/xml duality, and add that, to me, having autocompletion for the xml ids inside custom components with vscode makes that duality a breeze to work with 👍
  • m
    using the previous Ian panels example, if the `LineSettingsPanel`custom component class builds the previous xml, we could do something like this:
    Copy code
    haxe
var panel = new LineSettingsPanel();

mainHaxeUIApp.addComponent(panel);

panel.homeView.hide();
    at least in vscode we have autocomplete for what I've done, when calling 
    panel.homeView
    and for every public property/method of the custom component and sub custom components... like Ian I make several custom components (and respective XML) for all UI representation and that makes simple/complex UIs very easy to maintain
  • b
    yeah, pretty much how i do things, keep all things nice and isolated and easy to "move" about
  • p
    I hated xml layout, then I finally took the blue pill or was it red? Anyways it is much better for a large project in my opinion. Manager changes where things go. Boom custom component moved in xml (3 minutes). 4 hours later the boss knows!
  • m
    @best-agent-85158 if I do something like your app, and do the UI only by code, it will be spaghetti everywhere in sight 😅 (note: I'm talking of my coding, not yours @best-agent-85158)
  • b
    tbh mine is pretty organized, but from the start - i rewrote 4000 lines of code for that
  • b
    well, i didnt rewrite code, i rewrote the entire project
  • b
    like started a new one
  • m
    yeah, but in my case I don't know if I can be so organised like you, doing all the UI by code, at least with a medium to a large project
  • b
    btw, the way i orgnized everything: i made a center for all main event dispatching & listening, which can accept events with 
    EventDispatcher.dispatch
    . you can fill whatever event needed there, and it will execute certine predefined functions. you can access everything from anywhere, because the main editor of the app is being assigned to a static variable, and the editor contains public links to every single tab
  • b
    every single tab appears in a different file, and some files have 2 classes to seperate listener logic and graphics:
    Copy code
    haxe
class Toolbox extends ToolBoxGraphics {
 //listeners & public functions
}

class ToolBoxGraphics extends Grid {
  //public vars here
}
  • h
    Is it possible to add Icon on selected item for the dropdown box component ? At example in the image below, the Haxe logo on selected item with text Haxe
  • m
    well, the xml and css in my custom components, is the graphic representation and the custom class has the logic, the difference is, if we have 10+ components to deal in that custom component, I only have to make changes to the xml/css, but it will come down to personal preference in the end
  • b
    thats currently not possible, however, it is something i want to add, i dont see any harm in using an ItemRenderer for the button contents also - but currently, no its not possible, the dropdown button is a button, and its only text
  • b
    i still have nightmare flashbacks of trying to build professional interfaces in swing, all in code. Loads of "add this, add that" type of stuff, then 3 months later, you need to add a new button (or worse an new panel that means you need to move everything about), total headache...
  • b
    i ended up kinda indenting the code to show the level of the components 😄
1...103510361037...1687Latest