citro3d
                                
                                
                                
                                    citro3d copied to clipboard
                            
                            
                            
                        [RFC] citro3d documentation
This is a work in progress pr to finish the documentation for citro3d. You can check out the pr's docs here: https://oreo639.github.io/citro3d/index.html
Warning: This may contain mistakes or poor wording choices. Comments are welcome.
Thank you for the review. Sorry about the typos.
Just copying these down so they don't get buried. What still needs to be looked into:
- [x] https://github.com/devkitPro/citro3d/pull/54#discussion_r609072718
 - [x] https://github.com/devkitPro/citro3d/pull/54#discussion_r609071984
 - [ ] https://github.com/devkitPro/citro3d/pull/54#discussion_r609101744
 
This PR looks great! It may have gotten a little stale but would still be valuable to have. Any chance of it being revived and/or accepted + published? I have been using https://oreo639.github.io/citro3d/index.html as my go-to for citro3d docs and would love to see this upstreamed and officially published.
If it would be helpful, I can try to review or help any other way, but I am of the opinion that any amount of docs is better than none! Let me know if there's any way to help see this PR through across the finish line.
Thanks for the comments.
Here is a brief overview of what needs to be finished:
- shadows and lighting
 - proctex
 - fog
 
These are things I would preferably experiment with and write applications using them and I just haven't gotten around to that yet.
Here is a list of other remaining tasks in order from most to least important:
- Proofreading (grammar mistakes are certainly an issue, but I am primarily concerned about misleading/incorrect descriptions and missing notes/pitfalls that may not be obvious to new users of the library, one that I have since been informed of but need to commit is 
C3D_SetScissor(), as an example, which requires you to take into account the rotation of the screen) - Better descriptions (There is no point in having 
doFoo() -> Does foo.type descriptions) - Grouping everything. (similar to citro2d)
 - Possibly provide a basic description on how to use the library (similar to libtheora's documentation)
 
I'm sorry about the delay, my attention has primarily been focused on other projects, but I'll try to look into this more in two weeks give or take. Any comments or feedback would be greatly appreciated.