https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    and your alternative is to have haxeui process the css -> scss at compile time in a macro or something?
  • h
    Well.. I think I'm kind of stuck with HaxeUI processing it during run-time which may be less than desirable, but it's what I'm working with right now
  • h
    And it's because I'm trying to see how I can make styling for Coconut over HaxeUI more seamless
  • b
    so coconut doesnt like haxeui css?
  • h
    Well, the coconut compatibility with HaxeUI is bare-bones by the very definition. I mean, there might actually be less than 3-400 lines of code (possibly less tbh) to make coconut work on top of HaxeUI. So you can imagine just how "integrated" it is. It's not that Coconut doesn't like HaxeUI css . . . it's just that the only thing Coconut supports as far as the XML-tags goes is whatever extends from 
    haxe.ui.core.Component
    and wraps its own helper methods around it.
  • h
    I believe the Style tag is not a component, but a sort of "meta" thing
  • b
    ah
  • b
    yeah... its not processed in the same way
  • b
    or or
  • h
    yeah none of that is supported
  • b
    maybe some others i cant quite remember
  • h
    yeah, like the tag
  • h
    That's not really a component I think
  • b
    yeah, data too
  • b
    can it use the haxeui xml parser?
  • h
    It quite possibly could, I think the only thing it "really" needs in order to work "properly" with HaxeUI is for tink.Hxx to understand how to interrop with HaxeUI and for Coconut to add some meta-fields to the real components (for tracking data changes). The meta-field /data-change tracking could probably stay how it is, but the thing I believe "really" needs to be done for real haxeui xml parsing would be the hxx implementation
  • h
    I actually believe it wouldn't be such a terribly difficult thing to do, but I'd have to understand some more details first. I think I get Hxx and Coconut's way of wrapping over HaxeUI for the most part, but I couldn't even begin to wrap my head around how HaxeUI does its parsing and how I could better integrate the two.
  • b
  • b
    so basically you call "new XMLParser("")" and a resourceResolver (if you want for things like )
  • b
    out of that you get a "ComponentInfo" which is basically all the component properties
  • h
    Ahh. So it appears that I was actually wrong about what the Hxx api was doing and what I thought Coconut was doing. So actually making use of the HaxeUI parser would probably not be the best thing to do for compatibility reasons . . .
  • h
    I'll need to do some more digging and playing around with the two technologies. But right now CSS is definitely the most nagging discontinuity between the two
  • h
    Well, I got a pretty seamless haxeui+coconut with CSS working now I guess haha
  • b
    via addStyleString?
  • h
    Yes!
  • h
    And Cix
  • h
    The only "immersion" break would be that Cix needs to make a backlog of all of the generated CSS requests until HaxeUI.toolkit was initiated
  • h
    I think I could make a macro to insert its own "init" function within Toolkits, but not worth it for me at the moment lol
  • b
    Cix?
  • h
1...147148149...1687Latest