egui
wgpu
egui | wgpu | |
---|---|---|
3 | 195 | |
1 | 10,995 | |
- | 2.5% | |
0.0 | 9.9 | |
28 days ago | about 1 hour ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
egui
-
Why Rust?
Anyone who's interested in the AccessKit integration can play with my work-in-progress branch: https://github.com/mwcampbell/egui/tree/accesskit
It's currently Windows-only, and I'm working on the big missing feature, which is text editing support.
-
UIs are not pure functions of the model
> A core premise of Cocoa, and MVC in general, is that UIs are a projection of data into a different form of data, specifically bits on a screen.
This is a tangent, but the implicit assumption that the UI is visual is just begging for a response from an accessibility perspective, so here goes.
Accessibility is very much an afterthought in native GUIs, not only in Cocoa, but also in Windows with the UI Automation API, and AFAIK with other native accessibility APIs as well. With these APIs, the assistive technology (e.g. screen reader) pulls information from the application (usually via the GUI toolkit), through repeated calls to methods defined by the accessibility API. Often the AT has to do several such calls in a row (and those often translate to multiple IPC round trips, making things slow). And the UI might change between such calls; there's no guaranteed way to get a consistent snapshot of the whole thing, as there is with a visual frame. On the application/toolkit side, these methods may return different responses from one call to the next, and the application or toolkit has to fire the right events when things change.
The web improves on this, in that accessibility information is conveyed through HTML tags and attributes. And yes, this is included in the output of a React component's render function. So while in practice, implementing accessibility may still be an afterthought, it's not an architectural afterthought as it is in native platforms.
One of my goals in AccessKit [1] is to work around this shortcoming of native accessibility APIs, particularly for developers of cross-platform non-web GUI toolkits. In AccessKit, the toolkit pushes a full or incremental accessibility tree update to the AccessKit platform adapter, which maintains the full tree in memory and uses that to implement the platform accessibility API. This even works for immediate-mode GUIs, as one can see in my proof-of-concept integration with the Rust egui toolkit [2].
[1]: https://github.com/AccessKit/accesskit
[2]: https://github.com/mwcampbell/egui/tree/accesskit
-
Raygui – A simple and easy-to-use immediate-mode GUI library
I can also report some modest progress on my own work on accessibility of immediate-mode GUIs. I have a branch of the Rust egui library [1] that has basic accessibility on Windows using my AccessKit project [2]. I do have a long way to go to make this fully usable and ready to submit upstream, especially when taking non-Windows platforms into account.
[1]: https://github.com/mwcampbell/egui/tree/accesskit
[2]: https://github.com/AccessKit/accesskit
wgpu
-
GPU Compute in the Browser at the Speed of Native: WebGPU Marching Cubes
Oh look it's subgroup support landing last week: https://github.com/gfx-rs/wgpu/pull/5301
- 3D and 2D: Testing out my cross-platform graphics engine
- Warp Terminal is now available for Linux
- Linux version of Warp terminal is here
-
Building the DirectX shader compiler better than Microsoft?
And wgpu has been doing this for years. Things like descriptor indexing are not exposed to the web but used by Rust (mostly) engines on native.
https://wgpu.rs/
-
New Renderers for GTK
If they used https://wgpu.rs/ they would get directx and metal for free (:
-
Show HN: WebGPU Particles Simulation
IIRC it was delayed multiple times. I think the first intent to ship from chrome was before 100 but they kept pushing it off. Firefox still does not support it. There are projects like wgpu[0] that wrap provide a higher level API and I have used some projects using it with no issues. WFIW I didn't see any issue with OP's demo either.
[0] https://github.com/gfx-rs/wgpu
- Deno 1.39: The Return of WebGPU
-
How do I become a graphics programmer? – A guide from AMD Game Engineering team
wgpu, the Rust WebGPU implementation is the bee's knees. https://wgpu.rs/ You can use it beyond the web.
-
There is anything like wgpu.rs for Zig?
There is anything like wgpu.rs for Zig? wgpu.rs is an abstraction on top of Vulkan, Metal, DirectX, etc...