https://linen.dev logo
Powered by
# haxe-ui
  • b
    heh heh, yeah, thats broken... not sure why... i really need to go over each of these and make sure they still work
  • b
    especially as they are likely and entry point for alot of people
  • b
    generally the single component ones should work (as i tend to update them more often) but the bigger demos atrophy pretty fast
  • a
    they do in my experience
  • b
    cool - well, ill make a note to fix the bigger ones... i think ill dump one of them... iirc kitchen-skink was the "main" one
  • b
    (but ill confirm that when i try them locally)
  • a
    by code editor, do you mean a haxe IDE specifically for haxui, or a tool to design guis?
  • b
    well, its just a code editor... you can use it for whatever you want
  • a
    oh so like vim but with a gui?
  • a
    i see
  • b
    thats what im using it for
  • a
    wow thats really cool
  • b
    but that part in the middle with the code in it, thats the code editor
  • b
    (ie, not the tabs and other panels)
  • q
    Hi, can you tell what's the canonical way of making a model available to nested components?
  • b
    i guess there is no canonical way... ive seen people use a few different way... custom mvc's, itemrenderers, custom components / views...
  • b
    ive been thinking to create another lib haxeui-mvc (or something)... but im just not sure its worth it since people tend to be pretty opinionated about that type of stuff
  • q
    I just wanna do injections through the constructors, if that's not too simple minded
  • q
    but, ack, how does that work when it's all macro stuff
  • b
    do you have like a basic (even psuedo code) example of what you would like to achieve, maybe i can tell you how i would go about it
  • b
    (maybe that would help, maybe not 🙂 )
  • q
    I mean, I'm happy to bubble events upwards for outgoings
  • q
    how does event propagation look?
  • q
    Is there anything going root to tip?
  • b
    they should propagate up, so are you talking about emitting events from a model for a view to listen for?
  • q
    I'm remembering now the quite painful flex initialisation protocol
  • q
    It's just (model,ui) -> ui
  • b
    right, but what are you trying to achieve, you change a prop on the model and ui changes, the ui changes and it updates the prop on a model?
  • b
    (just trying to understand / make sure we are talking about the same thing)
  • q
    You know, on the one hand not writing too much boiler plate, on the other hand not wanting too much JuJu
1...507508509...1687Latest