rust-tutorials/triangle-from-scratch

Drawing a triangle with no other crate dependencies.

triangle-from-scratch's Issues

initializing Vulkan

initializing Metal

using gamepads/controllers

Full quantified names for constants

It’d be nice to mention the full quantified name for C constants when they’re mentioned for the first time, i.e CS_OWNDC is Class Style OWNed Device Context

Mention the required background skill in the intro

we don't say what othe rust skill a person needs.

(probably just having read The Rust Book)

GL Loader System

Separate from initializing a GL context (very platform specific) is the issue of making that GL context even slightly easy to use (fairly platform neutral).

Basically you usually end up with a function like:

fn gl_get_proc_address(name: &[u8]) -> *mut c_void;

And from there you fill in a struct of pointers or you fill in some global static values.

// global fn style
glClearColor(1.0, 1.0, 0.5, 1.0);

// struct style
gl.Clear(GL_COLOR_BUFFER_BIT);

The global functions style is a hair easier to use, but the struct style connects the fns more closely to their context (which is essentially "more correct").

So we should have a lesson about how you do all this. We don't have to do the full thing necessarily, since our actual GL usage is very modest. We can just show people what they would do and then say "now go use the crate".

high quality Windows mouse input

https://twitter.com/gosamihai/status/1291116234638073858

using curses

this is a unix-y subject. you can use pdcurses on windows, but the point is more about having a little practice with man pages.

Reading a C constant definition?

https://rust-tutorials.github.io/triangle-from-scratch/opening_a_window/win32.html#creating-the-window introduces constants derived from C #defines. Earlier asides such as Reading a C struct declaration seem to imply the audience isn't assumed to know C - so it might be worth briefly noting what these look like in the original C headers (e.g. #define WS_OVERLAPPED ... / enum { ... }) and how the exact type these match to in Rust can be somewhat ambiguous / down to the author's own personal guesswork.

initializing OpenGL

• Windows
• Mac
• Linux

link wchar? from utf16 macro page

https://docs.rs/wchar/ is a nice pre-built crate so you don't have to roll your own for https://rust-tutorials.github.io/triangle-from-scratch/appendix/utf16_literals.html

initializing DirectX

• requires COM support

sound output

using WebGL

For WebGL, and general "web stuff", I think we could cave and use wasm_pack, and the associated proc_macro and such.

compute utf16 literal in const context

entropy from the OS

Using a console screen buffer

https://docs.microsoft.com/en-us/windows/console/console-screen-buffers

Win32 examples don't show the title

The win32 examples that handle the WM_NCCREATE event without using DefWindowProcW don't have their non-client area drawn properly, which means that they don't get the title text drawn.

Unsafe calls in Default implementation

Make sure all unsafe calls in Default implementation explains that the zeroed variant of the struct is valid

a Game Boy Advance ROM

an excuse to dabble with volatile / mmio, and also direct video memory drawing.

opening a cocoa window

Setup CI for the code

Currently the only CI is a github pages run when a commit goes to the main branch.

It would be better for bug catching if there was also CI to build examples and run tests. The only major complication would be that not all examples build on all platforms. Possibly we could narrow the scope of lib testing and example building on each platform so that win32 bins are only built on windows and so on.

discuss windows_subsystem

In our tutorials, we set the windows subsystem:

#![cfg_attr(not(debug_assertions), windows_subsystem = "windows")]

but with no explanation why, or what's going on with that.

opening an x11 window