https://linen.dev logo
Powered by
# haxe-ui
  • b
    do you want me to merge these doc updates? I mean, are you still adding to the PR?
  • b
    I Lso want to change some code (like minimal things, @:enum for example)
  • b
    So yeah you can merge it
  • b
    change @:enum to what? I think @:enum is still needed for haxe 3.x isnt it?
  • b
    Oh wait does haxeui support haxe 3?
  • b
    it does currently yeah, someone asked about it ages and ages ago, and since its little to no effort to support it, it makes sense to
  • b
    Oh nice
  • b
    It is interesting how many ppl still us haxe 3 tho
  • b
    i dont actually know how many people are actually still on haxe3, but it was mentioned a few months ago in an issue, and now the GH actions run things through 3.4.7 to make sure
  • b
    About the pr, you can merge it. I need to take some time learning what every variable does...
  • b
    will do... nice one!
  • b
    (merged)
  • b
    What is Column exactly? Is it just a list of composites that can sorted?
  • b
  • b
    (technically neither header nor column actually have to be part of tableview ofc)
  • b
    so techncally its just a fancy button title for tables?
  • b
    gotcha. imma doc that. what about the sorting stuff?
  • r
    this is one of them "rtfm" things, but just to point out: If you don't include hscript, you don't get any errors in haxeui... it just draws nothing but the labels all on top of each other
  • b
    what are the sortField & sortable fields doing in 
    Column
  • f
    Hi @best-agent-85158 , to see what haxeui components dp, it's reat to readdhttps://community.haxeui.org/t/haxeui-v1-4-released , https://community.haxeui.org/t/haxeui-v1-2-released , https://community.haxeui.org/t/haxeui-v1-3-released/ etc
  • f
    sort is explained in the last link 🙂
  • b
    @bright-gpu-74537 im taking it upon myself to document the entire Style class, but i also have a question: can i add the 
    applyTo
    function i was talikng about:
    Copy code
    haxe
public function applyTo(components:Rest<Component>) {
  for (c in component) c.customStyle = this;
}
  • b
    usage:
    Copy code
    haxe
var s:Style = {padding: 5, verticalAlign: "center"}
s.applyTo(vbox, hbox, mygrid, image1, image2);
  • b
    i think ill use inline docs for this because things wont be long
  • b
    So i dont have a problem with it per se, i do kinda feel its what the css engine itself is there to accomplish: 
    #vbox, #hbox, #mygrid, #image1, #image2 {padding: 5, verticalAlign: "center"}
    . But if people are happier using a code only approach, its no skin off my nose 🙂 That said, i do think it should be a static extension rather than in the 
    Style
    class, it keeps it simple and its also an explicit "using" then which means we dont have to care so much about compatibility issues (like for example i dont think rest args are supported on haxe3, or even all versions of 4)
  • b
    huh youre right, theyre a haxe 4.2 feature
  • b
    everywhere theres a white dot its a field from the 
    Style
    class:
  • b
    so yeah, i would use a static extension (StyleTools) and even #if haxe4.2 (i cant remember the best way to do that now)
  • b
    not sure i understand what you mean
  • b
    #if (haxe_ver > version("4.2"))
1...100810091010...1687Latest