GraphicsProgramming / GraphicsProgramming/RVPT

Project structure not exactly a library.

Open
#58 7 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
C++
Stars
82
Forks
8
PR merge metrics
No merged PRs in 30d

Description

The current code works more as an executable which is just a model loader. What do we want to do?

I personally see two options we can do.

1. Not make this a rendering library, but just a path tracer. (Which can make pretty things), and maybe turn it into some type of SDK in the **far** future...
2. Focus on making this a library.

I would personally go for option one, as we do not have the most amount of features currently. And it would be a much better idea to make the images pretty first, and then worry about making it a library. Versus having to do both at the same time.

Just opening because this is something that needs to be discussed, but it's yet to be something **serious**, but something to mention.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.