An experimental library design based on what is described in this blog post: High level libraries.
Excerpt:
High level libraries is the idea that Rust libraries can be written in a such way for game engines, that makes them very easy to use and can be composed together without adding complexity. I think the expression “high level” is awfully inaccurate, but I have not yet come up with a better word for it. Unfortunately I don’t have the libraries yet to show what I mean, but I hope to explain something about it in this post.
...
What are high level libraries?
This is something I am excited about!
When I say “high level” I mean different from “normal” or “low level” because of the way the library is used, not because it is further away or closer to the hardware. It is because such libraries usually are designed for higher concepts that involves bigger pieces of game programming, and they can be combined to build the features you want. So “high level” means something like “high level game library for Piston” and does not refer to programming in general.
A high level library requires just a few lines of code to set up, and adds functionality to the application without adding complexity.
This is writeup of the state of high level library experimentation. I plan to gradually push this idea further, and make it the default way of introducing Piston. Libraries that does not depend on the Piston core won't be affected, and generic libraries does not have to be used with current objects. This way we can keep the existing philosophy of modular libraries that fit well together, but also improve the "user friendly" part.
An experimental library design based on what is described in this blog post: High level libraries.
Excerpt:
Comment from discussion:
Other Resources