https://linen.dev logo
Powered by
# haxe-ui
  • m
    That's a heaps thing with the arrows since it is just a listview box. It's certainly nowhere near perfect yet and I'm sure my monkeys can improve their coding 🙂 I wanted to get something out there.
  • b
    sure, cool... i think the heaps arrow thing is a bug of some description in haxeui... havent seen it in my ui tests... but maybe i havent been looking for it
  • m
    I need to figure out how to offset the filenames in the listview. I'll fool with it when I pick up that project again. I'm going to go back and work on my Flixel one for a bit and hopefully get that most of the way done for release
  • o
    i can't get the "heaps template" to work (made from 
    haxelib run haxeui-core create heaps
    ). it gives me a slue of errors that seem like type errors
    Copy code
    haxeui-heaps/1,3,1/haxe/ui/backend/AssetsImpl.hx:22: lines 22-26 : { width : Dynamic, height : Dynamic, data : hxd.BitmapData } should be hxd.res.ImageInfo
    is the haxelib version good for heaps, haxe-ui, etc .. or should i be using git (also i'm 4.2)
  • b
    you'd need to use git version of heaps
  • b
    or maybe its the other way round... git version of haxeui-heaps
  • b
    ... i forget which... but basically, git version of both
  • o
    haha ok let me try. i just git heaps and it didn't work, so i'll play around with which to git
  • b
    yeah, i think it got it the wrong way round... i think you need git haxeui-core and haxeui-heaps... i had thought i created an up-to-date haxelib, but i recall someone having the same issue
  • b
  • b
    (last two comments)
  • o
    and that worked for me. thanks!
  • b
    right... so looks like i need to make a haxelib release for haxeui-heaps... its strange though, as i usually bump all the versions together and that error is from ages ago... so maybe the haxelib release failed... ill make a note
  • d
    Is there a recommended backend for targeting web and desktop?
  • d
    There seem to be five different backends that target both and I can't find a comparison of the pros/cons of using each.
  • b
    it depend what you are after really
  • b
    each backend, generally, piggy backs an existing framework
  • b
    (haxeui-html5 being an exception)
  • d
    I'd like to end up with a standalone binary on desktop and a simple set of html/js on web.
  • b
    right, so you could do a few things really: * you could use haxeui-hxwidgets to create a native app, haxeui-html5 to create a web app (they will look different) * you could use openfl, flixel, nme, kha, heaps and target both web and desktop (they will look the same) * you could mix and match all of the above
  • b
    oh you could also use haxeui-html5 and and create an electron app too
  • b
    if you use one backend, your arent "locked into it" until you start using things that are specific to that framework
  • b
    so you can build different version of your app with different backends (i do it all the time)
  • b
    (eg)
  • b
  • b
    (maybe that will help somewhat?)
  • d
    I'm having trouble getting anything other than the html5 backend working.
  • d
    I got the heaps ones to build, but it doesn't seem like hashlink is available for my system (nixos) so I can't actually run the desktop version.
  • d
    Flixel didn't seem to make a hxml file, just a project.xml
  • b
    right, yeah, you'll need hl to run an hl app 🙂
1...579580581...1687Latest