App structure/modularity improvement possibilities

[kaosat-dev]

So as I was looking for ways to solve the modularity app structure issues I found a very interesting article and project :

http://badassjs.com/post/40691367335/voxel-js-a-minecraft-like-block-based-game-engine
http://voxeljs.com/
https://gist.github.com/maxogden/5147486

The project in itself seems fun, but what caught my eye mostly was HOW they deal with modularity using Browserify : I am honestly impressed , as it seems like it would solve a lot of issues , and would allow people to contribute a lot more easily .
What do you think ?
(I will do a small proof of concept to see how well this kind of methodology works, but so far I like it a lot).

As far as ease of coding and workflows go, this might also be interesting:
http://www.vagrantup.com/

[MauricevanLeeuwen]

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)

[kaosat-dev]

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.