On Wed, Jun 7, 2023 at 1:02 PM Alon Zakai wrote:
> As I said at the start, it does become somewhat annoying to fully maintain
> with WasmFS. We've found a way to work around some of that in
>
> https://github.com/emscripten-core/emscripten/pull/19452
>
> but more remains (right now I'm looking at
As I said at the start, it does become somewhat annoying to fully maintain
with WasmFS. We've found a way to work around some of that in
https://github.com/emscripten-core/emscripten/pull/19452
but more remains (right now I'm looking at some closure issues related to
it). It is just awkward to ac
On Wed, Jun 7, 2023 at 10:29 AM Alon Zakai wrote:
> Yeah, this is tricky. I agree with Floh that our early ports of glfw etc.
> are of limited use. Ideally they'd all be done like SDL2, that is, be in
> upstream + use emscripten HTML5 C APIs as much as possible, to get
> consistent input event ha
Yeah, this is tricky. I agree with Floh that our early ports of glfw etc.
are of limited use. Ideally they'd all be done like SDL2, that is, be in
upstream + use emscripten HTML5 C APIs as much as possible, to get
consistent input event handling etc., which is a common issue as you said,
Sam.
Stil
On Wed, Jun 7, 2023 at 5:36 AM Floh wrote:
> I wonder whether most of those old "portability wrappers" shouldn't be
> deprecated tbh (SDL2 might be special because it has "official" upstream
> support now?).
>
> Those wrappers were very helpful in the beginning to get things started,
> but for in
I wonder whether most of those old "portability wrappers" shouldn't be
deprecated tbh (SDL2 might be special because it has "official" upstream
support now?).
Those wrappers were very helpful in the beginning to get things started,
but for instance (as far as I noticed) Dear ImGui was running i
