https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    cool - thanks for the info... hxLibGit2 is the way to go here i think anyway, its faster, and just more "correct"... ... plus, its a useful lib in its own right - so good excuse to add missing bits (like "status")
  • b
    Yh, that's fair
  • b
    so it doesnt actually upload the release (yet), but it does package it (doesnt test it)... just trying to get the "flow" right... feels pretty good so far 🙂
  • b
    Looking really cool!
  • b
    yeah, not bad for a day and a half 🙂 More important though is that it will be silly useful (for me at least). I 100% could have already manually released all the haxelibs, but where is the fun in that? And this will also be more useful in the long run
  • a
    Funny realisation
  • a
    I think you single handedly may have the largest collection of maintained haxe code in the entirety of haxe
  • b
    heh heh, you saying that because of libgit2?
  • a
    i'm saying that because i don't think most people personally manage more than 3/4 libs at most and you're over here managing at least 10 😂
  • a
    the uploading to haxelib process is a "meh step"
  • a
    I wonder if an app like this would make people update their haxelibs way more often
  • b
    certainly would me! Esp if / when i add "batch submit"... so i can just right click on the group and select "Submit", give them all the same version, all the same release notes and bosh... im done
  • b
    what do you mean?
  • a
    a "chore" not in a bad way, just extra
  • a
    a "eh, i'll do that later" kind of thing 😂
  • b
    oh right, i get you, i thought you meant in the app, you mean in general... yeah, 100%
  • b
    its even worse for haxeui since there is a bunch of libs... its really not complex, but its just laborious enough to find other things to do 😄
  • a
    yeah, the process is just a lot of steps and adds resistance
  • b
    exactly... even if they were all batch files, thats a bunch of batch files... though i could then run all of those in sequence... but mistakes can be made (like releasing uncommited files, ive done that a few times)
  • b
    and ofc, updating haxelib.json and then committing it ... all in all, as you say, a chore
  • b
    "Right Click HaxeUI Group" -> "Submit" -> "Set Details" -> "OK" -> "Get on with life" 😄 ... ... much better
  • a
    😄
  • c
    Have you (or @bright-gpu-74537 ) considered using CI/CD for this task? It's really pleasant to see things happen automatically and even get automatic changelogs and releases
  • a
    if i did have a lib to maintain on haxelib i think I would be more incentivised to look into automating the process, by either some kind of home server bot or using github actions and have it update based on some version change so i didn't have to manually bother with it
  • a
    Generally, the libs i publish i'm mostly the user for it - so i'm generally happy with it just being on github lol
  • b
    yeah, its not a bad idea to use an action, for sure - but this app is useful in other ways too, ie, haxelib management - if you do have a, say, "publish all haxeui libs" action, can you just run that manually?
  • b
    (like you can with a Jenkins job for example)
  • c
    Yes, github actions can have manual triggers in adition to the automamted ones
  • c
    I already have an almost working flow for one of my libraries for automatic publishing to haxelib, but it is failing with a weird error.
  • h
    Getting a really unspecific error from haxeui when I build to html5
    Copy code
    txt
/usr/share/haxe/lib/haxeui-core/git/haxe/ui/macros/Macros.hx:403: characters 63-71 : () -> Void should be Unknown<0> : haxe.ui.events.UIEvent -> Void
/usr/share/haxe/lib/haxeui-core/git/haxe/ui/macros/Macros.hx:403: characters 63-71 : ... For function argument 'listener'
src/MainView.hx:108: lines 108-331 : ... Defined in this class
1...152415251526...1687Latest