Shatur

@davidrevoy@framapiaf.org Happy new year!

Created a branch that targets the bsn branch. All tests pass, and all examples compile: https://github.com/simgine/bevy_replicon/pull/660 I haven't used the bsn macro inside the examples yet because its syntax might still be unstable. I'd like to wait a bit. The branch also includes long-awaited resource replication support! See the replicate_resource* methods. I ported bevy_replicon_renet as well: https://github.com/simgine/bevy_replicon_renet/pull/74 #bevy

@LineageOS Just flashed to my 6 year old device. Thank you for your hard work and happy new year!

@bevy@mastodon.social 🎉 In the release, you mentioned that the new widgets are headless, as are the rest of the Bevy widgets. But is there a plan to provide a default style? Feathers is a separate crate right now, but is that because of the current API limitation that couples styling with the widgets themselves?

@seshpenguin@social.sineware.ca I wish more distros supported these retro consoles! I found ROCKNIX a bit opinionated for my taste. It would be nicer to have something like Plasma Mobile or Phosh with an option to open ES-DE.

@laund@wetdry.world @bevy@mastodon.social I know, but last time I asked they were marketed as widgets tailored to the editor and explicitly marked as non-game widgets.

@laund@wetdry.world @bevy@mastodon.social When you start developing a game, you don't care about the style. If I use feathers, the migration to plain UI later will be painful, since it's a different widget set. But using plain UI is also a pain because I need to style it. This is why I'm asking developers about their pans. In other game engines you have a default style that you can customize. It's intended to be used in games. You start with the default style and later just theme it.