https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • a
    but, its a pretty decent start
  • b
    like unicode, bidi, color fonts, inline images
  • b
    accessibility features
  • a
    yeah sure, but all of this is kind of a bit of a meh thing to point out
  • b
    wym
  • a
    no one is going to 0-100% a fully working text input
  • a
    you're going to start from somewhere, and incrementally
  • b
    u said most of it was already done
  • b
    im just saying its not
  • a
    ahhhhhhhhh
  • a
    okay then
  • a
    well, it is a good enough place as any
  • a
    given that haxeui can easily map to native targets
  • a
    I don't think my comment was out of place
  • a
    html, it uses html text input
  • a
    native it uses a native text input
  • a
    mobile backend i believe uses native text input
  • a
    composite (which is what I was referring to) would use the custom text input
  • a
    because there's no "native" text input to composite backends
  • b
    html is the best text input for haxe-ui right now
  • a
    that's because it is just a normal html text input
  • b
    umm.. yeah
  • b
    i think we're having different conversations
  • b
    gg
  • a
    it seems so
  • a
    my initial idea is only referring to composite backends
  • a
    because there's no way one needs to make a custom text input where native input is available
  • b
    there is if it's missing a feature u need
  • b
    but yeah i was talking mostly about the API, not really about haxe-ui
  • b
    the API is most of the work
1...159515961597...1687Latest