https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    it all basically ends up as that, even if you use styleString
  • b
    congrats 🙂 Looks interesting, still never sure how it fits into haxeui 🙂 - there is no chance im going to offload drawing to a 3rd party lib and not use what is available to the host framwork
  • b
    a note btw, soon 
    style
    will become 
    computedStyle
    and 
    customStyle
    will become 
    style
    ... im dragging my feet on this as i know its going to break alot of things, but it does need to be done
  • f
    Thank you for the heads up.
  • b
  • b
    shows the power of macros too... small oversight, just a little "ill get back to this in a minute" and things do weird stuff
  • b
  • f
    At quick glance, would it have something to do with ' name: "Button" ' in line 794 causing a button to be created instead of a textfield?
  • b
    heh, yeah, basically, whenever you use "short class names" in haxeui "script" a macro will go through, try and find a registered class and just replace it with the full class name, it just means you can be less verbose in "script"... ... ... ... however it doesnt matter what class you use, the macro will always replace it with a button 🤣 🤦‍♂️
  • f
    Maybe it could be kind of a plugin ? If there were a way to extend the CSS to use an external library ( Nanjizal for drawing) or Vision for filters. 💨
  • b
    css doesnt "draw" anything though - it instructs a renderer what to draw
  • b
    i mean, i you could certainly create your own backend for all of it, that would use lib X to do the rendering
  • b
    but im not gonna do it... im already juggling "too many" backends
  • f
    I wasn't thinking in term of a whole backend . But by shadowing the filters by example you ( not you as in Ian, but as in someone) could easily add Vision filters. I was wondering about how you could do it with Nanjizal's library, yeah maybe just shadowing a few haxe files in the specific composite backend . Nanjizal is an artist, I'm sure he's imagining all the insane UI he could do with it.
  • b
    i think the filters is a valid one, and its defo something i think should be abstracted out... ie some type of "filter handlers" (with a fallback)... but i still dont really see how "this draws pixels" (as opposed to this manipulates framework pixels for the filters) is relevant without a full backend
  • b
    my understanding is that Vision is taking images and changing them into something else, where as Justins stuff is like an abstracted drawing framework... which haxeui kinda already is... so i just fail to see where it slots in
  • f
    I'm not sure . In fact I first thought Nanjizal's library as an SVG replacer ( he talked about some svg and here about some xml) , if it's the case, it's kind of just another other format of an image. And I thought cool, could be a way to add SVG on some other backends than openfl, but in fact it would maybe better to have @orange-van-60470 insight 😆
  • o
  • o
    The library is currently wired to put on canvas with the correct color twizzle. But it is more an abstract pixel drawing tool so you can put onto any image.
  • o
    so it is not another backend more of a drawing tool for any backend that has pixel support.
  • o
    so it is a GL fallback
  • o
    and helper
  • h
    I'm trying to style Label text with element at the top of my xml. I can style it ok inline on the element but if I try from a element for the document I'm failing. My guess is I have the selector wrong. Should it be 
    Label#id { styles}
    - doesn't work. Neither does simple selecting 
    #id {}
    . I'm guessing I need more hierarchy. But ``#id text` didn't work either. I thought I have this working elsewhere but I'm clearly wrong.
  • f
    You can use stylenames for example. You can read the beginning here https://gist.github.com/Shallowmallow/0b3f1974eda3a94ccc9ea1d1939a2d98 . ( Makes me think I have to update it with my local version and some some PRs for haxe-ui guides ...)
  • h
    Many thanx. I forgot about styleName but still odd id's don't work. I'll try it in a bit. Also thanx for the cheat sheet - I want to define a separate case for anyway
  • h
    duh ! I have styleName elsewhere - man ! my XML is too big
  • f
    I think, if I undersood your post well, it's because you you do 
    #id textname
    but you must do 
    #textname
  • f
    (But not sure you can always post an unworkoring example in the builder .)
  • h
    I could and I have it in the playground but it has extraneous stuff in it too - I kinda use the playground as a designer/scratchpad
  • h
    thanx again
1...133813391340...1687Latest