https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    so still not right, seems you need to review your remove / dispose impls
  • a
    yeah
  • a
    need to know a bit more about ceramic here
  • a
    maybe what i want is active 🤔
  • a
    oh this is weird, nvm i guess?
  • a
    not sure why i'm getting duplication here
  • a
    He are there any examples of accessing haxui properties like textfield text from haxe code or binding XML views to classes? because there is very little documentation on that despite it being the most important part of the library
  • b
    not a huge amount im afraid, this might be the best thing atm: http://haxeui.org/api/guides/custom-components.html
  • b
    it goes through some of the options
  • a
    binding a class to an xml is pretty simple
  • a
    Copy code
    hx
package ui;

import haxe.ui.containers.VBox;

@:build(haxe.ui.macros.ComponentMacros.build("assets/ui/page.xml"))
class Page extends VBox {}
  • a
    where what you extend is the root component of the xml
  • a
    Also many of the guides describing Haxeui’s various features are completely blank
  • a
    yeah, docs aren't present
  • a
    it's super capable, but, not many docs are available
  • b
    yeah, i keep meaning to "fill in the blanks", but its never a 10 minute job and im (seemingly) always snowed under with more pressing (and more interesting 🙂 ) things
  • a
    writing docs are a bit of meh task, but the way i feel is, if i "consider" writing docs i want to do them well so i don't have to revisit them and then realise it will take too much time 🤣
  • b
    the biggest problem i have with writing docs, except for the fact its just boring, is that since i made it, i tend to oversimplify things - like something that is super obvious to me isnt mentioned, etc. That said, it makes sense to start the docs, because editing docs is a helluva lot simpler than starting them
  • b
    plus, all those sections are coming from a GH repo now... which reminds me, i think there is a new set of docs i need to generate
  • b
  • b
    ah, its not merged yet
  • a
    there's also formatting of docs... etc etc
  • f
    Oh forgot to answer, youcan merge it already and I ll complete it ( and clip the images ) little by little
  • a
    it makes my brain tired 🤣
  • b
    cool - nice one
  • b
    yeah, its never a quick job, though as i mention, i think a good approach is do something and then refine it
  • f
    The most difficult part is starting (and finishing) but incomplete documentation is still pretty useful
  • a
    yeah, you're probably right. Maybe something like a blunt "want to achive this? here's the code" might be enough
  • b
    yeah, getting some type of text / structure on there is useful
  • b
    yeah, agreed
1...155815591560...1687Latest