Closed ozkriff closed 4 years ago
@icefoxen (https://github.com/rust-gamedev/rust-gamedev.github.io/issues/231):
https://rustgamedev.com/episodes Saw this and was surprised that it wasn't included in the newsletter already, then realized it was brand new. Haven't actually listened to it yet though, so maybe it's not good. XD Will listen to it and see how it is.
📜 Updated the structure/list of sections!
I'll take Egregoria :-)
Happy to write a bit about blitz-path, I'm honoured you want to include it.
It might be better to wait to list Crankstart until the Playdate SDK is generally available. Right now it not usable by anyone who isn't in the closed developer program.
Taking: Event Chaining as a Decoupling Method in ECS Could we also add Minigene inside of the Library & Tooling Updates section? https://git.jojolepro.com/minigene (updating the readme with more details soon)
I'd be happy to write a small bit on hexasphere
.
I'd be happy to work on: "Roguelike with Amethyst" talk + blog posts .
Unfortunately shader-types is fundamentally broken, and I would advice everyone not to use it. 😢
Happy to write about "chargrid rl tutorial 2020"
@ozkriff I completed a game jam this past month and just posted a retrospective. If you don't mind, I'd love to write a short blurb in the Game Updates section. Figured I'd ask before sending in an unannounced PR!
@cwfitzgerald oh, ok, removed shader-types from the plan.
@rtsuk :ok_hand: sure, removed Crankstart from the current newsletter - ping me when the SDK is released!
@jojolepro @ecton great! Added Minigene and Chillscapes sections to the plan!
I wrote up a quick thing on RustGameDev Podcast, for the second episode. PR #234 Just added it in the "learning materials" section, but it's listed in the main issue as having its own section... where do we want to put it?
I'll work on Bevy!
I'll write about the smooth voxel stuff.
will take spirq
and inline-spirv
. thx!
Will be glad to write about NeoCogi's libs :)
I just saw I got mentioned here for rspirv-reflect
, I can definitely write something about that, thanks!
Just noticed this, I'd be happy to write on "Writing NES Emulator in Rust"
I will take Dimforge and Rapier!
Thanks for the Egui mention - I've made a PR for it.
I'll write about wowAddonManager
Opened PR #250 to include Mun's updates in the newsletter
Hello, I was recommended to submit this snippet of code for inclusion in the newsletter by @workingjubilee It's an example on how to use custom panic hooks and allocation error hooks to handle panics and OOM gracefully. How to cleanly handle panics and OOM in a GUI application
ncurses
on Unix and a bundled pdcurses
on Windows. If you're looking to make a terminal-based roguelike (or any other terminal-based game), give it a try.I'll write something for Dwarf Seeks Fortune
.
Sorry for the slow response again. :( If the deadline is still this Saturday, I can write something for A/B Street by then.
Hey, sorry I missed this. I'll try writing something for SIMple Physics
I'll write something about Piston updates, Nano-ECS and UI experiments.
Hello, I was recommended to submit this snippet of code for inclusion in the newsletter by @workingjubilee It's an example on how to use custom panic hooks and allocation error hooks to handle panics and OOM gracefully. How to cleanly handle panics and OOM in a GUI application
@AlexApps99 sure! Added to the plan; feel free to send a PR.
If possible could you add SIMple Mechanic's good first issues to the requests for contribution section?
@ozkriff on second thought, although the example seems to work, rust-lang/rust#51245 points out that alloc functions are annotated with #[rustc_allocator_nounwind]
, so it could potentially lead to bugs or undefined behavior.
It doesn't seem to affect Desktop platforms, but I would prefer not to recommend this until it is 100% safe.
@AlexApps99 :ok_hand:
Grabbing akigi, ecs_bench_suite, Amethyst, mochi, optik-rs, sia, aaand intellij-ron.
The final PR: #274 ("Newsletter 13") - everyone is invited to review :)
:tada: https://rust-gamedev.github.io/posts/newsletter-013 :tada:
This issue was written by more than 30 people, that's crazy! :-D Huge thanks to all contributors and reviewers, you are awesome!
Next coordination issue: #278 ("Newsletter 14")
Feel free to suggest sections!
If you want to help writing the newsletter:
source
branch (example: #75)I'm hoping to release this newsletter on 2020.09.07, so a soft deadline for all section PRs is 2020.09.05.
Current structure/status (I'll try to keep this updated):
Final steps: