GraphicsProgramming / GraphicsProgramming/RVPT

Project structure not exactly a library.

未关闭
#58 7 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
question
主要语言
C++
星标
82
派生
8
PR 合并指标
30 天内没有已合并 PR

描述

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.

贡献指南

这个仓库没有索引到贡献指南

调研方向

No files, tests, or concrete entry points are named. Review the current C++ executable and model-loader structure, then look for a maintainer decision on whether the project should remain a path tracer or become a library; done requires an agreed direction and concrete implementation scope.

由索引模型根据 Issue 内容生成。

评估

技术栈
cpp
领域
computer-graphics
Issue 类型
重构
难度
5/5
预计耗时
一周以上
活跃度
停滞
描述清晰度
需要澄清
新手友好度
20/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。