https://linen.dev logo
Join DiscordCommunities
Powered by
# haxe-ui
  • b
    this much is true, but its laborious and its hard to not prefix everything with "take a look at the code"
  • b
    that said, i know that most people would rather have a step by step guide rather than trial and error and looking at code of the lib
  • b
    its just "hard" to isolate the steps... in many ways, i think the author(s) of any lib / framework are the worst positioned to offer starting help about it, but its a necessary thing
  • b
    I personally prefer a short and concise startup guide and then code examples showcasing various features. Sometimes I would like to also see practical examples as to where and why some feature is usable/good to use.
  • b
    for me personally, the hard part is usually motivating myself to start writing
  • b
    once I'm in the process of writing, it's not so bad
  • b
    the problem is that with software, there's lots of "starts" because you have to keep it up to date with changes 😄 (thinking of the vshaxe wiki here in particular..)
  • b
    yeah, all true
  • b
    for me, im kinda the opposite... i start with a "right, going to write some docs!", thats the easy part... then about a paragraph in im like "meh... i might just write some code"
  • b
    interesting 😃
  • c
    I usually just throw in some point-form stuff quickly, which is a infinite improvement of the documentation already (with base is zero)
  • c
    and hopefully someone (me?) will improve it step by step
  • b
    "point-form"?`
  • h
    I assume point form means, this code example leads to this example which builds on this example and there you go, your abcs. At least that's what I would hope lol
  • b
    yeah, i agree Kevin, just get something out there...
  • b
    i think (hope) that the custom component readme works like that (ie, "point form" - if that does mean one example leads to another): https://github.com/haxeui/haxeui-guides/blob/master/custom-components.md
  • b
    that way the intention anyway
  • h
    That looks pretty good actually, I'll take a better look when I wake up for sure
  • u
    @bright-gpu-74537 The armory zui readme is a good example of a brief but descriptive doc.
  • u
    But what you just linked is pretty good and very descriptive.
  • f
    so haxe-ui is a complete stand alone rendering thing right?
  • u
    @fancy-city-440 no the backends do the rendering bit( well from what I understand) because you need to use a backend to use haxeui
  • f
    yes I understand that
  • f
    I mean Haxe-ui is in and of itself not dependending on other things than those backends?
  • f
    im interested in the kha backend, hasn't been updated in a while
  • f
    just wondering if there are other dependencies
  • u
    Look at the new-component-method branch. That is usually the branch that is the most up to date( last commit was in march)
  • u
    And yes haxeui only depends on the backends for rendering
  • f
    a day ago actually 😛
  • f
    oh you mean for kha
1...171819...1687Latest