I vote for separating the library into submodules as well like:groverburger wrote: ↑Sat Jan 16, 2021 10:55 pmYeah I understand that complaint - I'm considering doing kinda what p5js does and having a global/non-global version of the lib.
The main reason the lib is global is because I pulled the files that are now called g3d out of a project I was working on and I didn't change them to be non-global.
I'm worried changing this that would break compatibility, and I've already broken compatibility once.
I also think having the lib in the global namespace may make the source code easier for people to read and understand themselves, which is something I aim for with g3d.
So, I'm open to more feedback here.
(Also if anyone is wondering I mistyped and titled this update v1.2 when I should have typed v1.1 -- oops!)
Code: Select all
local Model = require("g3d.model") local Camera = require("g3d.camera") local Loader = require("g3d.objLoader") -- and so on
Anyway im looking forward to using this library to learn basic 3d gamedev soon!
PS. I would be willing to help with refactoring the code to make more modular in case you decide to make it as suggested above.