These are chat archives for bjz/gfx-rs
Actually, I'm not sure if this talk was even meant to be about architecture:
how we're structuring Voyager and hoping to use the most of Rust to accomplish our goals.
We can always change the title though.
@photex I'd really like gfx-rs to stay away from the concept of Material... It's a big topic, and however you approach it, I don't see how you can cover everyone's needs....
The big question that I mentioned is how do we implement a generic way for gfx-rs to allow clients to provide parameters for the programs they run (what I'd like to call "Program environment". UBO or not is a technical detail (and we can go straight without it for now given the time constraints for the demo).
As a straight-on solution (that doesn't require too much thinking), I can port the dictionary approach (Enviromnent is
Map<String,Parameter>, where Parameter is an enumeration of supported types (int, vector, matrix, texture, etc).
I think that as it stands now gfx-rs is not quite satisfying the first of its goals:
Simple, lightweight implementation