App structure/modularity improvement possibilities about coffeescad HOT 2 OPEN

Considering structure and modularity: why is the CAD kernel and frontend in one repository? And why did you split it from OpenJSCad instead of sending your modifications upstream?

(I found the CoffeeSCad CAD kernel in another repository also, but it isn't used as such)

from coffeescad.

Kernel and frontend in same repo was for "historical" and convenience reasons : coffeescad was originally only a front end to openjscad so the kernel was just here to keep things simple.
That is going to change soonish though as I am working on refactoring and spliting out the kernel.

Sending modifications to upstream was the original plan but :

• i was not a fan of the "one big file with all code " approach of openJscad
• the kernel in coffeescad now has a big difference to openjscad : all transforms CHANGE the current object instance while openjscad returns a NEW object from each transform.

from coffeescad.