Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Ben Morris
@bendmorris
I'm not completely disappearing but this way I won't block you
I would ask though that you still open PRs for larger changes - you can merge your own PR after at least a day or so if no one has any feedback, but I think it's a good practice to still put the PR up
Matrefeytontias
@matrefeytontias
Of course
I don't mean to work on my own
Ben Morris
@bendmorris
:+1: welcome to the committers, honestly I should've added you sooner
Matrefeytontias
@matrefeytontias
Haha glad to hear it
Better late than never :thumbsup: thanks !
Jarrio
@Jarrio
Hello, is there a guide or some documentation about how to introduce a new backend to haxepunk? I would like to try making a kha backend at some point soon
Ben Morris
@bendmorris
no guide or documentation, as it hasn't been done before - your best bet is to use the OpenFL/NME backends as a spec and reimplement them for Kha
Jarrio
@Jarrio
My main source of confusion is how is a backend actually selected?
If I included the library in kha, how does haxepunk know which library to use vs which to not
I don't see syntax like #if nme anywhere
Ben Morris
@bendmorris
it's based on include paths - for OpenFL/NME this is driven by the include.xml
you'd create a backend/kha directory, add that to your source paths, and it should provide the same classes as the other backends
Jarrio
@Jarrio
OH I see. I missed that file
Jarrio
@Jarrio
Is the flash backend required?
Ben Morris
@bendmorris
flash backend is a common base for OpenFL/NME since they both have similar APIs
Jarrio
@Jarrio
Ah I see, it's meant to serve as a wrapper around the lower level API's right?
I wouldn't have to mess with that I guess?
Disar
@Disar
@Jarrio im here now too
my first instinct was to have a haxepunk.graphics.hardware.kha package
Jarrio
@Jarrio
That would go against the agnostic setup of it all
Disar
@Disar
I don't see how though, because GL isn't agnostic
it's a specific implementation where hardware.kha would be another implementation
Jarrio
@Jarrio
I'm not sure it should be taken as literal openGL
The idea is we basically follow the openGL api and create wrappers to recreate the functionality
I think
Disar
@Disar
Well it's just weird then because if you look into haxepunk\graphics\hardware\opengl you can see it's gl "wrapper"
Jarrio
@Jarrio
I was looking over how Robert added the kha heaps backend and that's basically what he did
Disar
@Disar
so I'm assuming other implementations go into \hardware\
Jarrio
@Jarrio
I believe those files get overwritten by the files in the backend directory
Disar
@Disar
Well if @bendmorris could elaborate that would help alot, now it feels like we are speculating
Jarrio
@Jarrio
We definitely are
Disar
@Disar
it does look like RenderBuffer.hx uses those GL packages specifically
The other files under graphics/hardware look to be higher level abstractions
Disar
@Disar
I guess im missing something but how do I set haxepunk project for vscode to pick up the sources for the haxe cache
navigating trough code is a bit clunky now
Disar
@Disar
@Jarrio looks like you're right
just copy the structure, I guess the biggest confusion was just the GL prefix
We also have to handle asset loading
nvm on that cache building, got it figured out
X.A.N.O.Z.O.I.D.
@XANOZOID
Hello, is there a way to change the window size for desktop? I can't seem to find one.
X.A.N.O.Z.O.I.D.
@XANOZOID
I found that the XML file can change the size, but was hoping for a API specific solution
X.A.N.O.Z.O.I.D.
@XANOZOID
I had to do it using nme.Lib.stage.resize( WIDTH, HEIGHT ); . . . any better way?
X.A.N.O.Z.O.I.D.
@XANOZOID
Was HaxePunk-UI ever any good? Would it be worth trying to bring it up to date?
I haven't seen what its capabilities are . . .
Matrefeytontias
@matrefeytontias
Cross-post from the HaxePunk channel on the Haxe Discord
Let it be known : after looking at the state of HaxePunk, and seeing that we have taken the route of hardware rendering anyway, we decided with @Ghouly The Ghost that we'd rather ditch OpenFL/Lime and NME and rewrite HaxePunk without the backend philosophy to instead only support Kha
For us it makes sense since Kha is the one to provide multiple backends, so it sounded silly trying to do its work when it's already done.
Being extremely optimistic, I'm aiming at reaching a working state with as little change to the HaxePunk API as possible by the end of the month
tl;dr nothing changes for the end user ; for the HaxePunk devs, the backend system will be no more and HaxePunk will only be powered by Kha
This is not a definite decision, I'm posting this here to open a discussion, especially regarding the other contributors to HaxePunk
@bendmorris @MattTuttle