zemeroth VS femtovg

i've used both in zemeroth: i migrated it from ggez to macroquad mostly because ggez at that time didn't support android and web targets. but i'd say that the main difference is tech stacks they're using: while ggez extensively reuses the existing rust gamedev ecosystem (winit, wgpu, rodio, etc), mq was written mostly on top of minimalist or its own specialized libraries (see miniquad).

nope, /u/not-fl3 is the author. i'm just using it in my zemeroth.

Trying to get back to the development of my turn-based game Zemeroth: going to finish the first iteration of settings screen for configuring widgets' size and screen offset, and get back to writing devlogs for the v0.7 release.

Depends on CI system you prefer. Here's Zemeroth's Github Actions release config for example: https://github.com/ozkriff/zemeroth/blob/master/.github/workflows/release.yml

Tutorial is based on a public test of zemeroth game.

zemeroth: a 2D game with desktop versions, but also a wasm online version

Oh, I was really waiting for this episode as my Zemeroth game shares a lot of history with mini~ and macroquad. Here're some of my thoughts.

Femtovg (https://github.com/femtovg/femtovg) which uses OpenGL to render

Congrats! I don't want to diminish the accomplishment, but have you seen femtovg? It seems like it's probably well-aligned with your needs.

I'm currently using femtovg for vector graphics in my games, and I would like to get into bevy by porting one of my game prototypes using it to bevy.

I use femtovg It's a simple vector graphics engine having all the important features you probably want from a 2D rendering engine: simple shapes, images, text

https://github.com/femtovg/femtovg/pull/5

Before Power10 was done, IBM actually asked us Raptor users about proposals for useful machine code instructions to add to it. I replied that I’d like to have hardware UTF-8 de-/encoding but they wanted a more detailed proposal and I never got around to write it. I’m not even sure that this would be worthwhile, but I see UTF-8 de-/encoding everywhere in the code I write and would like it to approach memory read/write speeds.

I was very disappointed to learn that they had gone more proprietary with Power10 so I would not have been able to use those instructions anyway. What a pity!

In my actual code, I'm using a library called femtovg that is a Rust port of a C library for 2D rendering. But In the blog post I kept the example simple to keep it relevant for people who might want to use Web Workers + WASM for other things; didn't want to get hung up on femtovg for someone who had never heard of it. As you say, if you all you need to do is basic 2D manipulations of a canvas that are supported by the native API, then you likely don't need WASM.

You guys should also check out the femtovg project, a 2D rendering API that sixty fps relies on.

https://github.com/femtovg/femtovg

It's a decent starting point for trying to build your own toolkit.

I have recently added a wgpu backend but for now it lives in my fork https://github.com/adamnemecek/femtovg

run the demo with `cargo run --example wgpu_demo --release`.

Also join the femtovg discord https://discord.gg/V69VdVu

I'm involved with the femtovg project. We are definitely looking for contributors. Join the discord channel.

It's not a GUI framework but I'm involved with this project called femtovg, it's a Rust nanovg port. I've recently added a wgpu backend. Run the demo with cargo run --example wgpu_demo --release. Some people have been using it for their own UIs, e.g. tuix. I think that you should consider rolling your own GUI toolkit, it's not that bad and you'll appreciate the control.