https://linen.dev logo
Powered by
# haxe-ui
  • b
    @User - yeah, i mentioned before there simply is no text input (yet) for haxeui-flixel... its simply doesnt have an impl (and there is nothing inside flixel to handle it, so will likely have to roll out my own as i did with kha or use something else like @User 's )
  • t
    Ah sorry I missed that!
  • b
    np 🙂
  • t
    I'm not sure how backends are implemented
  • b
    @User - you could always just change the default theme in haxeui-flixel?
  • t
    otherwise I'd have a look
  • b
    well, it doesnt have to be in a backend... if you make a input text field that works in flixel then its likely that will be able to be incorporated into the haxeui-flixel backend
  • b
    (its how i went about it with Kha - first i made a general kha only, no haxeui, text input field https://github.com/haxeui/haxeui-kha/blob/master/haxe/ui/backend/kha/TextField.hx and then i incorporated that into the backend system)
  • b
    so if you come up with something, defo let me know as, even if its pretty basic, its a good start that can be built upon over time
  • b
    other alternatives are to port that kha one to flixel
  • b
    also @User - if you were creating a so called "pure" haxeui app (ie, using HaxeUIApp and using no framework specific calls directly) then you can just try out all the backends you want
  • h
    @User thanks a lot for all of the info, I tried out the fixed menu and now it works perfectly which is great!
  • h
    so is a backend really needed in order to make a haxeui only app?
  • b
    definately... haxeui-core is a ui abstraction and it needs a backend for its implementation
  • h
    alright I got that now
  • b
    but if you use the general "HaxeUIApp" classes, you dont ever need to use any framework specific stuff and core + backend can take care of everything meaning you can just add another build to the app and voila, you have a new app using a different backend
  • b
    (i do it all the time to test things)
  • b
    haxelib run haxeui-core create [somebackend]
  • h
    oh wow that's great
  • b
    if you run that multiple times in the same dir with a different backend param it will add build files for that backend, but the actual source of the application wont be touched
  • h
    do you need an emulator in order to debug haxeui-android?
  • b
    you can use emulator or phone, i tend to use phone
  • b
    it reminds me i need (want) to move that backend to use the new jvm target rather than hxJava which is what it uses currently
  • h
    I don't know what the new jvm target is, would it let you run the app on the pc or is it just faster/better?
  • b
    it a new haxe target that creates bytecode directly rather than java source that then has to be compiled to byte code via the java compiler - the compile should be much faster and maybe also execution... no idea... it had some issues with it last time i tried that as far as im aware have been fixed but i have tested again
  • h
    nice, I'll have to try some more backends out someday
  • b
    👍
  • t
  • b
    yeah, part of flixel-ui... obviously haxeui-flixel wouldnt want to bring in all of flixel-ui, but maybe i InputText.hx could be created based around that...
  • b
    although, rather interestingly FlxInputText doesnt look very linked to flixel-ui at all
1...435436437...1687Latest