alteous

Support for custom extensions

10

There are two formally supported extensions by the crate: `KHR_materials_pbrSpecularGlossiness` and `KHR_lights_punctual`. As discussed in #226 there is no way to retrieve any other extension data. I believe it's now...

Document how to upload whole buffers and/or make it easier

1

glTF binary buffer data is designed to be uploaded straight into GPU memory without modification however it's unclear how to do so. We should either document (i.e. create an example)...

Make mesh::Reader usage more clear

1

There is sufficient [module level documentation](https://docs.rs/gltf/0.12.0/gltf/mesh/index.html) however this isn't communicated on the [buffer::Reader](https://docs.rs/gltf/0.12.0/gltf/mesh/struct.Reader.html) page.

Fix lifetime return values

1

#264 partly fixes a long standing issue of unnecessarily restrictive lifetimes returned by some functions. The crate may be more user friendly if we applied similar fixes throughout.

RFC: Document supported environments

4

I don't have the time/patience/knowledge/resources to support every environment under the sun. I'd like to make it clear in the documentation which environments are officially supported, which environments are not...

Document semantic versioning guarantees

3

We have three crates under this repository: `gltf`, `gltf-json`, and `gltf-derive`. The main crate is `gltf` and is designed to adhere to [semantic versioning](https://semver.org/) guarantees. The other two crates are...

RFC: Re-implement crate using a toml-driven code generator

2

Based on my conclusions in #198, this tracks the re-implementation of the `gltf_derive`, `gltf_json`, and `gltf` crates using a code generation program (written in Rust, of course!)

Project logo

2

#### Rules 1. No usage of the official glTF logo ([this one](https://raw.githubusercontent.com/KhronosGroup/glTF/master/specification/figures/gltf.png)) or any other Khronos trademark. 2. Don't break rule 1.

Standard validation error codes

3

Inspired by the [official glTF-Validator issues](https://github.com/KhronosGroup/glTF-Validator/blob/master/ISSUES.md) list, we should have our own set of (compatible?) validation error codes. We have a whole lot of [test data](https://github.com/KhronosGroup/glTF-Validator/tree/master/test/base/data) to ~~steal~~ take advantage...

Continuing discussion from #175: We have rudimentary validation checks upon import to ensure that the wrapper library doesn't panic when unwrapping `None` et cetera. It may be worth considering performing...