https://linen.dev logo
Powered by
# haxe-ui
  • b
    They are expensive tho
  • b
    yeah, im going to go a little "mad" with my next PC
  • b
    I got one at a discount, 1tb nvme
  • p
    Compiled at runtime, HL does JIT compilation.
  • b
    right right
  • b
    Was like 130usd
  • b
    so @powerful-morning-89 - are you also moving away from haxe now? Ive heard you talking about rust and kinc more and more
  • p
    Maybe, maybe not. I'll probably keep using Haxe for some things.
  • b
    gotcha
  • b
    @bright-gpu-74537 if I make a haxe -> haxeui xml parser/interpreter and transpile it to web assembly, can a haxe code option be added to the websites playground?
  • b
    Because now, you can only make components with xml
  • r
    (sorry to be harping on about treeviews but) I just noticed that there's no removeNode method - if I need to remove nodes, am I just required to be using a datasource?
  • b
    im not sure im understanding
  • b
    is there not a removeChildNodes or something?
  • b
    its 
    clearNodes
  • b
    but i agree, its not the most helpful, you might want to actually remove a single node
  • b
    pretty much transform things like this:
    Copy code
    haxe
var vbox = new Vbox();
vbox.addComponent(new Checkbox())
    into:
    Copy code
    xml
<vbox>
  <checkbox/>
</vbox>
  • b
    i mean, sure if you think you can get that to work, but i dont think its simple thing, and im not sure what it would add
  • r
    Yep, there's clear nodes, but my use case here is the user deleted the thing specified by a node
  • b
    yeah, thats fair - leave it with me, api experimental so for sure there will be holes in it
  • b
    i can do the initial type isolation & detection with regex, and the hierarcy shouldnt be that horrible to make if i have type info
  • b
    so something like "parentNode.removeNode(someNode)" basically?
  • r
    Yes, as well as being able to delete root nodes, I suppose. At the moment you add them just via supplying a dynamic to addnode. I include the related entity's unique id in that dynamic and use that for working with selections, but I'm not sure if there's a more general method to specify a node that doesn't rely on its sort order
  • b
    so by-the-way, you can just use "removeComponent" to remove child nodes, im going to add removeNode also though as semantically it makes more sense
  • r
    Aah, I wasn't sure if that was for nodes or for like, if you've added other elements via an item renderer
  • r
    Gotcha
  • b
    yeah, i wasnt either till i looked at the code, which is why i think removeNode is better, even if its basically just an alias
  • b
    @bright-gpu-74537 my plans: 1. newline on every 
    ;
    2. get type information with 
    ~/var +([\w+?):(\w+?)/
    3. get type information with 
    ~/(\w+?) *= *new +(\w+?)\(\)/
    4. get properties via matching var names with the props after the 
    .
    (
    varname.someProp
    ) 5. bundle that to an XML file
  • b
    its basic, but should be enought to test UI with haxe coe
  • b
    de
1...102410251026...1687Latest