https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    yeah, for the most part MDI isnt usually a thing... especially for simple apps... but im just starting a project where they have 100s of forms, and have them open all the time and are constantly switching between them, so MDI is certainly a must... well, maybe not a must but not having it would lead to friction that simply isnt needed
  • b
    they generally have one form open fullscreen at a time, so you could argue you dont need all the sizing and ordering stuff... but well, i got carried away 😄
  • f
    your "carried away" is everyone else's feature library, so go nuts
  • b
    haha...
  • b
    im happy with this.... still need to do some more, for sure... close / minimize dont work, no events dispatched from the window manager etc... but not bad for a day 🙂
  • i
    that looks great
  • p
    Now turn that into a full blown wayland compositor :P (Or an X11 WM if you're old school)
  • b
    ... sure, i got a couple of hours free next weekend... job done 😄
  • p
    Here is a weird thing http://haxeui.org/builder/?e3320fc9 The layout is buggered. At the top of the code, from the .label style remove width:100%; And it is fine http://haxeui.org/builder/?15e92021
  • p
    makes sense logically (labels are used inside of other components) but it breaks everything
  • b
    i think it makes sense that 
    .label { width: 100% }
    breaks everything (layoutwise), no?
  • b
    you are basically saying "all labels must now take up the full size of their parents", and some of those parents are autosized...
  • p
    Yes from the framework perspective. From an end developer perspective I chased my tail on that one since I added it and hadnt compiled for 2 hours.
  • p
    lesson learned: Dont style global objects
  • p
    at least not label
  • p
    carelessly
  • b
    > Yes from the framework perspective from a logical perspective, no? Im not sure how haxeui can guard against this > From an end developer perspective I chased my tail yeah, i mean, random global css that applies to all components can do bad things for sure... you could also do 
    * { width: 0, height: 100%}
  • b
    just to "clarify" the issue: http://haxeui.org/builder/?841e083c
  • b
    so you were basically doing "button2" to every label
  • p
    Yep.
  • p
    The only answer I could think of was to flag all haxeui core components to ignore css because hoseyhosey is an ass
  • p
    Anyways, I didnt think anything would come of it. Mostly pointing out the obvious I guess
  • b
    hahaha... 
    -D haxeui_hosey_guard
    ... which would warn about certain css 
    WARNING: are you sure hosey, you mean 100% for all .labels
    ? 😄
  • p
    lol, yep! I'll update my git now
  • b
    i mean, i get why it flummoxed you, but that the same time, i dont really think there is anything haxeui can do about it... i mean, if you go 
    * { width: 100px; height: 100px}
    then yeah, all components will be 100x100... haxeui cant really say "hmmm, that seems off", maybe its totally what you wanted
  • p
    agreed
  • e
    what backend is this?
  • b
    haxeui-html5
  • b
    should be the same in any composite backend, but untested so far... i doubt there would be a difference though
  • h
    I'm testing which has a "Hide help" checkbox in the bottom left. Notice when you click the "Hide help" checkbox and the help is revealed the two elements at the bottom left move up the screen. When you hide it then they move down. I want them at the bottom of the screen regardless of whether the help box is visible or not. How do I do that ?
1...129913001301...1687Latest