Render API wrapper rework thoughts

hnisula / ducklib

A library made out of ducks

1 stars 0 forks source link

Render API wrapper rework thoughts #17

Open hnisula opened 2 years ago

hnisula commented 2 years ago

Should they handle stuff themselves or just act as containers?
Move away from virtuals to simply matching API wrappers?

hnisula commented 2 years ago

As I now know more about what object needs what API object, this is easier to fix. A rule like: Construct X with the "higher" objects it will need and let it do all work it can itself?

hnisula commented 1 year ago

https://www.gamedev.net/blogs/entry/2265481-oop-is-dead-long-live-oop/

https://github.com/hodgman/dod-playground/blob/f42290d0217d700dea2ed002f2f3b1dc45e8c27c/source/game.cpp#L146 "Instead of components looking up siblings, link during construction"