morphorm
matchbox
morphorm | matchbox | |
---|---|---|
5 | 8 | |
238 | 818 | |
2.1% | - | |
6.5 | 8.7 | |
about 2 months ago | 29 days ago | |
Rust | Rust | |
MIT License | 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.
morphorm
-
What’s everyone working on this week (1/2023)?
I started working Rustycan - a small UI framework that focuses on developer ergonomics and uses other frameworks (such as egui/druid/html) for the rendering, except for the layout which I'm planning to use morphorm.
-
taffy 0.1: a fully-documented, actively maintained UI layout library to replace the abandoned stretch crate
That said, I'd be interested in migrating towards something closer to the Hierarchy trait that morphorm has pioneered. If this is something that's interesting and important to you could you make an issue?
-
Bevy and Dioxus are collaborating on stretch2: a revived UI layout algorithm
jkelleyrtp has been experimenting with other UI layout strategies, including SwiftUI. On my end, I really want to see morphorm support (based on subform): initial experiments are promising, and it's "refreshingly simple".
-
Bevy 0.6
There's a few critical subtasks here: - determine the data flow model we'd like to use for our UI. We'd like to integrate tightly into the ECS, but need to figure out how to reduce the boilerplate and improve reliability around working with hierarchies. - swap our layout library. Our current dependency stretch implements the flexbox algorithm, but is unmaintained and has critical bugs :( The three main options here are to fork flex, move to the new morphorm crate, or write a layout library from scratch - consider rearchitecting our UI to be more flexible and compositional: splitting the massive Style component into several parts and moving to a "UI is a collection of behaviors" paradigm - build out more widgets! - more docs and examples!
matchbox
-
Announcing lavagna v2, a collaborative blackboard made with bevy and WebRTC
The “collaboration” feature is achieved thanks to matchbox crate, a peer-to-peer WebRTC networking library.
-
IronBoy: High accuracy GameBoy emulator written in Rust and available in the browser via WASM
Consider using https://github.com/johanhelsing/matchbox to help with the WebRTC problem, I hear good things about it
-
Show HN: Hathora – Multiplayer Game Development Made Easy
https://github.com/johanhelsing/matchbox
Even then, you'd cover only some very specific use-cases of multiplayer game-making.
-
[Showcase] wasm-peers: easy-to-use WebRTC networking wrapper for WASM
That's the approach taken by the matchbox project, and it's done pretty well.
-
Bevy 0.6
In theory, it should also be possible to support browser-native crossplay that way. I did some work on supporting that, but I'm currently stuck on an issue with webrtc-rs.
What are some alternatives?
rfcs - Suggest changes to Bevy and view accepted designs
bevy_egui - This crate provides an Egui integration for the Bevy game engine. 🇺🇦 Please support the Ukrainian army: https://savelife.in.ua/en/
taffy - A high performance rust-powered UI layout library
Yew-WebRTC-Chat - A simple WebRTC chat made with Yew
stretch - High performance flexbox implementation written in rust
bevy - A refreshingly simple data-driven game engine built in Rust
bevy_ggrs - Bevy plugin for the GGRS P2P rollback networking library.
bevy-website - The source files for the official Bevy website
bevy-kajiya - A plugin to use the kajiya renderer with bevy
sprawl - A high performance Rust-powered layout library [Moved to: https://github.com/DioxusLabs/taffy]
wasm-peers - Easy-to-use wrapper for WebRTC DataChannels peer-to-peer connections written in Rust and compiling to WASM.