https://linen.dev logo
Powered by
# haxe-ui
  • b
    myImage.getPixelAt(x, y)
    or something
  • b
    certainly seems useful
  • b
    Could be a nice addition
  • b
    yeah, agreed
  • b
    Also, I have loads of free time this week, might get to start writing docs for haxeui
  • b
    😮
  • b
    I fell like I've got familiar enough with most of the common interface so why not, I kinda like to write docs too
  • b
    any additions to the docs (or lack thereof) is, ofc, most welcome 🙂
  • b
    > I kinda like to write docs too you some type of masochist? 😄
  • b
    Also, github copilot really helps with docs, as it kinda just throws a barebones version of the docs after u finish variable
  • b
    Tbh I don't know how it got to me lol
  • b
    U can even look at my library, documented as hell
  • b
    interesting, never thought about using AI to fill in the docs
  • b
    It's not the best, but you can let it generate some bade for the docs and then change some words or add a sentence
  • b
    i really hate inline code docs, i know they are required, but i abhore them
  • b
    Like the 
    //
    ?
  • b
    i wish there was some type of system where you have a class "MyClass.hx" and then a "MyClass.doc" or something
  • b
    yeah, just hate the huge amounts of comments in, code
  • b
    i get its a "me" thing, but ive always hated it, wish it could be seperated
  • b
    I mostly try to keep everything understandable and write descriptive var name s to avoid that
  • b
    Writing online docs means that your code isn't really understandable if u look at it
  • b
    same, but most libs (no haxe libs, just in general) have like a 10 line description for a 20 line function, with inputs, return values, etc, etc
  • b
    you end up with this fooking huge files (line wise)
  • b
    It's different from normal docs, because with normal docs the user doesn't try to look at the source code
  • b
    Tell me about that
  • b
    yeah, i would argue generated docs are probably more important, but i just hate how they are "in the source"
  • b
    but its a required evil i guess
  • b
    When I released my lib with e markdown support thing, because I didn't complete the cross framework support I supplied guides on how to make those in less then 10mina
  • b
    Those guides are 90 lines long
  • b
    To be fare, they have quite a bit of code in them
1...100210031004...1687Latest